@nan0web/core
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small scoped package from established publisher; lack of Sigstore attestation is a process gap, not a security indicator. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @nan0web/core is a framework package, not a typosquat of cors; name collision is incidental. | ai | |
| dependencies | unvetted-dep:@nan0web/i18n | AI (dependencies): Sibling package in the same nan0web ecosystem; expected dependency. | ai | |
| dependencies | unvetted-dep:@nan0web/protocol | AI (dependencies): Sibling package in the same nan0web ecosystem; expected dependency. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 3 / 4 | |
| 1.1.3 | 4 / 4 | |
| 1.1.1 | 4 / 4 | |
| 1.0.5 | 2 / 4 | |
| 1.0.3 | 2 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
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.
v1.1.3
2 findingsPackage name '@nan0web/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
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.
v1.0.5
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.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.