@nan0web/co
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:@nan0web/db-browser | AI (phantom-deps): @nan0web/db-browser is a same-org runtime dependency declared in package.json; phantom-dep heuristic false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Same rationale: scoped org package, not a typosquat of 'got'. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same rationale: scoped org package, not a typosquat of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Same rationale: scoped org package, not a typosquat of 'cors'. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @nan0web org package; short name incidentally close to many 2-3 char packages, not an impersonation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same rationale: scoped org package, not a typosquat of 'joi'. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Same rationale: scoped org package, not a typosquat of 'zod'. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same rationale: scoped org package, not a typosquat of 'qs'. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 3 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 2 / 5 | |
| 1.1.3 | 0 / 7 | |
| 1.1.2 | 0 / 7 | |
| 1.1.1 | 0 / 7 | |
| 1.1.0 | 0 / 7 |
v3.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nan0web.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
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.