@artel/en-verstak
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped UI component package; tiny payload and missing metadata are consistent with its documented purpose. | ai | |
| phantom-deps | phantom-dep:verstak | AI (phantom-deps): verstak is a peer/config-level dependency for this UI framework package; phantom-dep is a stable false positive here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.96.26028 | 1 / 0 | |
| 0.96.26027 | 1 / 0 | |
| 0.96.26026 | 1 / 0 | |
| 0.96.26025 | 1 / 0 | |
| 0.96.26024 | 1 / 0 | |
| 0.96.26015 | 1 / 0 | |
| 0.96.26014 | 1 / 0 | |
| 0.96.26013 | 1 / 0 | |
| 0.96.26012 | 1 / 0 | |
| 0.96.26011 | 1 / 0 | |
| 0.96.26010 | 1 / 0 | |
| 0.9.26016 | 1 / 0 | |
| 0.9.26008 | 1 / 0 | |
| 0.9.26003 | 1 / 0 |
v0.96.26028
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26027
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.26026
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26025
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26024
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.26015
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26014
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26013
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26012
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26011
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.26010
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26016
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26008
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26003
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.