@ammolite/next
A Next.js plugin for Ammolite
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ammolite/integration | AI (phantom-deps): Same-org monorepo sibling; declared as runtime dep, phantom flag is a false positive for this package structure. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped Next.js plugin for Ammolite; not impersonating nuxt. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Unrelated to jest; name reflects Next.js integration for Ammolite. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Unrelated to knex; CSS-in-JS plugin with coherent metadata. | ai |
v0.1.4
2 findingsPackage name '@ammolite/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.