← Home

react-art

npm Repository Homepage

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).

100
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

fbreact-bot

Keywords

reactartsvgvmlcanvasjsx

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 420)

Hide prereleases
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
16.4.0 6 / 0
16.3.2 6 / 0
16.3.1 6 / 0
16.3.0 6 / 0
16.2.0 6 / 0
16.1.1 6 / 0
16.1.0 6 / 0
16.0.0 5 / 0
0.15.1 3 / 11
0.15.0 3 / 11
0.14.0 2 / 8
0.13.2 2 / 7
0.13.1 1 / 7
0.13.0 1 / 6
0.12.1 1 / 6
0.11.0 1 / 0
0.10.2 2 / 0
0.10.0 2 / 0
0.9.0 2 / 0
0.7.9 2 / 0
0.4.2 2 / 0
0.4.1 2 / 0
0.0.1 0 / 0
19.3.0-canary-fef12a01-20260413 3 / 0
19.3.0-canary-fd524fe0-20251121 3 / 0
19.3.0-canary-fb2177c1-20251114 3 / 0
19.3.0-canary-fa50caf5-20251107 3 / 0
19.3.0-canary-f93b9fd4-20251217 3 / 0
19.3.0-canary-f6a48828-20251019 3 / 0
19.3.0-canary-f646e8ff-20251104 3 / 0
19.3.0-canary-ed69815c-20260323 3 / 0
19.3.0-canary-ed4bd540-20260202 3 / 0
19.3.0-canary-ec9cc003-20251208 3 / 0
19.3.0-canary-eb89912e-20251118 3 / 0
19.3.0-canary-ead92181-20251010 3 / 0
19.3.0-canary-e8c63626-20260213 3 / 0
19.3.0-canary-e33071c6-20260224 3 / 0
19.3.0-canary-e0cc7202-20260227 3 / 0
19.3.0-canary-dd048c3b-20251105 3 / 0
19.3.0-canary-da9325b5-20260417 3 / 0
19.3.0-canary-da641178-20260129 3 / 0
19.3.0-canary-d763f313-20251210 3 / 0
19.3.0-canary-d7215b49-20251013 3 / 0
19.3.0-canary-d6cae440-20260106 3 / 0
19.3.0-canary-d2908752-20260119 3 / 0
19.3.0-canary-c9ddee7e-20251031 3 / 0
19.3.0-canary-c80a0750-20260312 3 / 0
19.3.0-canary-c7862584-20251006 3 / 0
19.3.0-canary-c137dd6f-20260204 3 / 0
Showing 100 of 420 Next page →

v19.2.5

2 findings
HIGH Missing gitHead — previous versions had it provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.2.4

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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 findings
HIGH Missing gitHead — previous versions had it provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.4

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.