@1001-digital/components.evm
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Org-internal component library; missing description is a style issue, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for org-internal packages; no other risk signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of an established @1001-digital monorepo ecosystem; sparse metadata is a style choice, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:qrcode | AI (phantom-deps): qrcode is a declared runtime dep; phantom-dep heuristic fires but it's likely used indirectly via TypeScript source. | ai | |
| phantom-deps | phantom-dep:@types/qrcode | AI (phantom-deps): Type-only dep; framework-scoped, stable false positive for this package. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 3.6.11 | 4 / 6 | |
| 3.6.10 | 4 / 6 | |
| 3.6.9 | 4 / 6 | |
| 3.6.8 | 4 / 6 | |
| 3.6.7 | 4 / 6 | |
| 3.6.6 | 4 / 6 | |
| 3.6.5 | 4 / 6 | |
| 3.6.4 | 4 / 6 | |
| 3.6.3 | 4 / 6 | |
| 3.6.2 | 4 / 6 | |
| 3.6.1 | 4 / 6 | |
| 3.6.0 | 4 / 6 | |
| 3.5.6 | 4 / 6 | |
| 3.5.5 | 4 / 6 | |
| 3.5.4 | 4 / 6 | |
| 3.5.3 | 4 / 6 | |
| 3.5.2 | 4 / 6 | |
| 3.5.1 | 4 / 6 | |
| 3.5.0 | 4 / 6 | |
| 3.4.0 | 4 / 6 | |
| 3.3.0 | 4 / 4 | |
| 3.2.1 | 4 / 4 | |
| 3.2.0 | 4 / 4 | |
| 3.1.7 | 4 / 4 | |
| 3.1.6 | 4 / 4 | |
| 3.1.5 | 4 / 4 | |
| 3.1.4 | 4 / 4 | |
| 3.1.3 | 4 / 4 | |
| 3.1.2 | 4 / 4 | |
| 3.1.1 | 4 / 4 | |
| 3.1.0 | 4 / 4 | |
| 3.0.3 | 4 / 4 | |
| 3.0.2 | 4 / 4 | |
| 3.0.1 | 4 / 4 | |
| 3.0.0 | 4 / 4 | |
| 2.7.0 | 4 / 4 | |
| 2.6.1 | 4 / 4 | |
| 2.6.0 | 4 / 4 | |
| 2.5.4 | 4 / 4 | |
| 2.5.3 | 4 / 4 | |
| 2.5.2 | 4 / 4 | |
| 2.5.1 | 4 / 4 | |
| 2.5.0 | 4 / 4 | |
| 2.4.3 | 4 / 4 | |
| 2.4.2 | 4 / 4 | |
| 2.4.1 | 4 / 4 | |
| 2.4.0 | 4 / 4 | |
| 2.3.0 | 4 / 4 | |
| 2.2.0 | 4 / 4 | |
| 2.1.4 | 4 / 4 | |
| 2.1.3 | 4 / 4 | |
| 2.1.2 | 4 / 4 | |
| 2.1.1 | 4 / 4 | |
| 2.1.0 | 4 / 4 | |
| 2.0.1 | 4 / 4 | |
| 2.0.0 | 4 / 4 | |
| 1.3.1 | 4 / 4 | |
| 1.3.0 | 4 / 4 | |
| 1.2.2 | 3 / 4 |
v3.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.