ace
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in lib/templates.js loads local template files by name — not arbitrary external input. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is ~14 years old, predates Sigstore provenance on npm. No provenance is expected and not a meaningful risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is typical for this 14-year-old low-maintenance package; not spam. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): ace and ajv are completely different tools with no overlap in purpose or user base. 2-edit Levenshtein distance is a false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 18 / 28 | |
| 1.2.0 | 18 / 28 | |
| 1.1.0 | 18 / 28 | |
| 1.0.3 | 18 / 28 | |
| 1.0.2 | 18 / 28 | |
| 1.0.1 | 18 / 28 | |
| 1.0.0 | 18 / 28 | |
| 0.0.2 | 4 / 0 | |
| 0.0.1 | 2 / 0 |
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.