@apify/input_schemanpm
- latest 4.0.6
- last known licence Apache-2.0
- stars 20
- assessment attempted 14 days ago
- GitHub evidence observed 14 days ago
- registry checked 14 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
Commits 90d
64
Open issues
5
Unanswered
1
Contributors
18
What the project says about itself
- Build provenance — the latest release, 4.0.6, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=22. Source: the registry.
- Publishers on the registry — 11. Source: the registry.
- Open milestones — 127th sprint - Tooling team (due 2025-11-17) 6/6 done; 128th sprint - Infrastructure team (due 2025-12-01) 1/1 done; 128th sprint - Tooling team (due 2025-12-01) 2/2 done; 128th sprint - Web team (due 2025-12-02); 129th sprint - Tooling team (due 2025-12-15). Source: the repository's milestones.
- OpenSSF Scorecard — 5.3 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 14 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-23 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@apify/input_schema)Watch it
Get told when @apify/input_schema changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.