react-art
React ART is a JavaScript library for drawing vector graphics using React. It provides declarative and reactive bindings to the ART library. Using the same declarative API you can render the output to either Canvas, SVG or VML (IE8).
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): The 'fb' spam-flagged maintainer signal is a false positive for Meta/Facebook's official React packages. Short README is expected for React sub-packages that defer to react.dev documentation. | ai | |
| provenance | no-provenance | AI (provenance): react-art is an official Meta/React package published via react-bot automation; lack of Sigstore provenance is a known gap for this publisher, not a malice indicator. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 19.2.5 | 3 / 0 | |
| 19.2.4 | 3 / 0 | |
| 19.2.3 | 3 / 0 | |
| 19.2.2 | 3 / 0 | |
| 19.2.1 | 3 / 0 | |
| 19.2.0 | 3 / 0 | |
| 19.1.5 | 3 / 0 | |
| 19.1.4 | 3 / 0 | |
| 19.1.3 | 3 / 0 | |
| 19.1.2 | 3 / 0 | |
| 19.1.1 | 3 / 0 | |
| 19.1.0 | 3 / 0 | |
| 19.0.5 | 3 / 0 | |
| 19.0.4 | 3 / 0 | |
| 19.0.3 | 3 / 0 | |
| 19.0.2 | 3 / 0 | |
| 19.0.1 | 3 / 0 | |
| 19.0.0 | 3 / 0 | |
| 18.3.1 | 4 / 0 | |
| 18.3.0 | 4 / 0 | |
| 18.2.0 | 4 / 0 | |
| 18.1.0 | 4 / 0 | |
| 18.0.0 | 4 / 0 | |
| 17.0.2 | 5 / 0 | |
| 17.0.1 | 5 / 0 | |
| 17.0.0 | 5 / 0 | |
| 16.13.1 | 6 / 0 | |
| 16.13.0 | 6 / 0 | |
| 16.12.0 | 6 / 0 | |
| 16.11.0 | 6 / 0 | |
| 16.10.2 | 6 / 0 | |
| 16.10.1 | 6 / 0 | |
| 16.10.0 | 6 / 0 | |
| 16.9.0 | 6 / 0 | |
| 16.8.6 | 6 / 0 | |
| 16.8.5 | 6 / 0 | |
| 16.8.4 | 6 / 0 | |
| 16.8.3 | 6 / 0 | |
| 16.8.2 | 6 / 0 | |
| 16.8.1 | 6 / 0 | |
| 16.8.0 | 6 / 0 | |
| 16.7.0 | 6 / 0 | |
| 16.6.3 | 6 / 0 | |
| 16.6.2 | 6 / 0 | |
| 16.6.1 | 6 / 0 | |
| 16.6.0 | 6 / 0 | |
| 16.5.2 | 6 / 0 | |
| 16.5.1 | 6 / 0 | |
| 16.5.0 | 6 / 0 | |
| 16.4.2 | 6 / 0 | |
| 16.4.1 | 6 / 0 |
v19.2.5
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: react-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.5
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: react-bot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.