@nan0web/log
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 not a security risk here. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped package; no impersonation of koa. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package; no impersonation of got. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped package @nan0web/log; Levenshtein match to 'glob' is a false positive for scoped namespaces. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package; no impersonation of joi. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package; no impersonation of zod. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package; no impersonation of pg. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 2 / 5 | |
| 1.1.1 | 2 / 5 | |
| 1.1.0 | 3 / 4 | |
| 1.0.1 | 2 / 4 | |
| 1.0.0 | 2 / 4 |
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.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.
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.