emoji-picker-element
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@nolanlawson/emoji-picker-element-for-tachometer | AI (npm-metadata): Intentional file: self-reference for benchmarking; documented in package.json; devDep only, no runtime impact. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.29.1 | 0 / 49 | |
| 1.29.0 | 0 / 49 | |
| 1.28.1 | 0 / 49 | |
| 1.28.0 | 0 / 49 | |
| 1.27.0 | 0 / 49 |
v1.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.