nano
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:nanoid | AI (typosquat): 'nano' is the canonical Apache CouchDB client name, not a typosquat of nanoid. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): 'nano' is the canonical Apache CouchDB client name, not a typosquat of pino. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 11.0.5 | 0 / 3 | |
| 11.0.4 | 0 / 3 | |
| 11.0.3 | 0 / 3 | |
| 11.0.2 | 0 / 3 | |
| 11.0.1 | 0 / 3 | |
| 11.0.0 | 0 / 3 |
v11.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.