art
Cross-browser Vector Graphics
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:got | AI (typosquat): art is a 13-year-old legitimate JS drawing library predating 'got'; 2-edit Levenshtein distance on a 3-letter word is a coincidence, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): art is a 13-year-old legitimate JS drawing library predating 'ajv'; 2-edit Levenshtein distance on a 3-letter word is a coincidence, not impersonation. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Version 0.0.0 is a historical artifact from 2011 when this convention was common; package has 173k weekly downloads and 13 years of history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata reflects 2011-era npm conventions; 173k weekly downloads and 13-year age confirm this is a legitimate, widely-used package. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition between known Facebook/React team members (sebmarkbage → zpao) in 2016. Both are established npm publishers. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.10.3 | 0 / 0 | |
| 0.10.2 | 0 / 0 | |
| 0.10.1 | 0 / 0 | |
| 0.10.0 | 0 / 0 | |
| 0.9.2 | 0 / 0 | |
| 0.9.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
2 findingsThis version was published by a different npm account than previous versions on 2016-01-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.