@aws-amplify/amplify-category-functionnpm
- latest 5.8.3
- last known licence Apache-2.0
- stars 2,875
- assessment attempted 6 days ago
- GitHub evidence observed 7 days ago
- registry checked 12 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
15
Open issues
741
Unanswered
130
Contributors
17
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 6. Source: the registry.
- Open milestones — AdminAuth 11/11 done; GraphQL Transformer improvements (RFC #1043) 1/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 7.1 / 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 6 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-31 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@aws-amplify/amplify-category-function)Watch it
Get told when @aws-amplify/amplify-category-function 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.