JavaScript sprintf implementation
67%
Total Score
50
100
86
83
Only one registry account has publish access. That is not proof of poor maintenance, but it leaves little apparent publishing redundancy when combined with inactive recent commits.
The repository is owned by an individual account rather than an organization, so the single maintainer represents the visible project backing and increases continuity risk.
The project has existed since 2013, but its latest release was in September 2023 and it has had no releases in the last 12 months, indicating a slow release cadence.
The repository recorded zero commits and zero active maintainers during the last three months, a concrete sign that maintenance has slowed.
One issue was opened in the last month, but no issues or pull requests were closed and no pull requests were merged during that period, suggesting limited active maintenance.
| Title | Versions | Severity |
|---|---|---|
CVE-2026-97058 sprintf-js is vulnerable to Improper Validation of Specified Quantity in Input in versions 0.0.0 - 1.1.3. | 0.0.0 - 1.1.3 | Medium |
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.