← Home

recharts

npm Repository Homepage
15
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

nikolasriebleckifercorkscreewe

Keywords

reactreactjschartreact-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() in createEventProxy.js is idiomatic Proxy handler code for transparent event forwarding — not obfuscation. Stable pattern for this package. ai
publish-pattern dormant-publish AI (publish-pattern): Recharts has 282 versions and 50.5M weekly downloads; it is not dormant. The finding reflects a publisher account gap, not package inactivity. ai
source-diff large-new-source-files AI (source-diff): 159 new files correspond to the added omnidoc documentation generation subsystem, consistent with the new omnidoc script in package.json. No malicious indicators. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() in umd/Recharts.js is standard webpack UMD bundle boilerplate, not a malicious dynamic code execution pattern. Stable false positive for this package. ai
dependencies unvetted-dep:victory-vendor AI (dependencies): victory-vendor is a legitimate dependency from the Formidable/victory charting ecosystem, appropriate for a charting library like recharts. ai
dependencies unvetted-dep:decimal.js-light AI (dependencies): decimal.js-light is a well-known decimal arithmetic library with no malicious history; appropriate dependency for a charting library. ai

Versions (showing 15 of 15)

Version Deps Published
3.8.0 11 / 91
3.7.0 11 / 85
3.6.0 11 / 85
3.5.1 11 / 82
3.4.1 11 / 80
3.4.0 11 / 80
3.3.0 11 / 81
3.2.1 11 / 81
3.2.0 11 / 81
3.1.2 11 / 78
3.1.1 11 / 78
3.1.0 11 / 86
3.0.2 11 / 85
3.0.1 11 / 85
3.0.0 11 / 86

v3.8.0

1 finding
LOW No provenance attestation provenance

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

v3.7.0

1 finding
LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.1

1 finding
LOW No provenance attestation provenance

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

v3.4.1

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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