@nan0web/ui
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 | missing-githead | AI (provenance): Likely CI/publish environment change; publisher has clean track record and no other malicious signals. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has clean track record; no CI provenance configured for this package across versions. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @nan0web/ui; not impersonating qs — Levenshtein false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @nan0web/ui; not impersonating joi — Levenshtein false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @nan0web/ui; not impersonating uuid — Levenshtein false positive. | ai | |
| phantom-deps | phantom-dep:@nan0web/log | AI (phantom-deps): Same-org dep; may be re-exported or used indirectly — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nan0web/core | AI (phantom-deps): Same-org dep; may be re-exported or used indirectly — stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @nan0web/ui; not impersonating yup — Levenshtein false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @nan0web/ui; not impersonating pg — Levenshtein false positive. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 6 / 19 | |
| 3.1.0 | 6 / 19 | |
| 1.12.3 | 5 / 20 | |
| 1.12.2 | 5 / 19 | |
| 1.12.1 | 5 / 19 | |
| 1.12.0 | 5 / 19 | |
| 1.11.0 | 5 / 19 | |
| 1.10.0 | 5 / 15 | |
| 1.9.0 | 5 / 15 | |
| 1.8.0 | 6 / 15 | |
| 1.7.0 | 5 / 15 | |
| 1.6.2 | 5 / 15 | |
| 1.5.2 | 5 / 15 | |
| 1.3.0 | 5 / 9 | |
| 1.1.0 | 4 / 8 | |
| 1.0.4 | 4 / 8 | |
| 1.0.3 | 1 / 10 | |
| 1.0.2 | 1 / 10 | |
| 1.0.1 | 1 / 10 | |
| 1.0.0 | 1 / 10 |
v3.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.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.12.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.11.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.10.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.9.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.8.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.7.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.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
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.2
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.