@escape.tech/graphql-armor-character-limitnpm
- latest 2.3.1
- last known licence MIT
- stars 588
- assessment attempted 17 days ago
- GitHub evidence observed 17 days ago
- registry checked 15 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
2
Open issues
3
Unanswered
1
Contributors
8
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=18.0.0. Source: the registry.
- Publishers on the registry — 5. Source: the registry.
- Security policy — published. Source: the repository.
Third-party facts checked 17 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-22 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@escape.tech/graphql-armor-character-limit)Watch it
Get told when @escape.tech/graphql-armor-character-limit 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.