@svgr/webpack
SVGR webpack loader.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): Babel preset loaded by convention in babel config, not direct import; standard pattern for this package type. | ai | |
| phantom-deps | phantom-dep:@babel/preset-react | AI (phantom-deps): Babel preset loaded by convention in babel config, not direct import; standard pattern for this package type. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-object-rest-spread | AI (phantom-deps): Babel plugin loaded by convention in babel config, not direct import; standard pattern for this package type. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-constant-elements | AI (phantom-deps): Babel plugin loaded by convention in babel config, not direct import; standard pattern for this package type. | ai | |
| dependencies | unvetted-dep:@babel/preset-react | AI (dependencies): Official Babel preset for React; well-known, widely-used package with no malicious history. | ai | |
| dependencies | unvetted-dep:@babel/preset-typescript | AI (dependencies): Official Babel preset for TypeScript; well-known, widely-used package with no malicious history. | ai | |
| dependencies | unvetted-dep:@svgr/core | AI (dependencies): Sibling package in the official SVGR monorepo by Greg Bergé; legitimate and expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): SVGR is a well-established project; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@babel/plugin-transform-react-constant-elements | AI (dependencies): Official Babel plugin; well-known, widely-used package with no malicious history. | ai | |
| dependencies | unvetted-dep:@svgr/plugin-jsx | AI (dependencies): Sibling package in the official SVGR monorepo by Greg Bergé; legitimate and expected dependency. | ai | |
| dependencies | unvetted-dep:@svgr/plugin-svgo | AI (dependencies): Sibling package in the official SVGR monorepo by Greg Bergé; legitimate and expected dependency. | ai | |
| dependencies | unvetted-dep:@babel/preset-env | AI (dependencies): Official Babel preset; well-known, widely-used package with no malicious history. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 8.1.0 | 8 / 4 | |
| 8.0.1 | 8 / 4 | |
| 8.0.0 | 8 / 4 | |
| 7.0.0 | 8 / 4 | |
| 6.5.1 | 8 / 4 | |
| 6.5.0 | 8 / 4 | |
| 6.4.0 | 8 / 4 | |
| 6.3.1 | 8 / 4 | |
| 6.3.0 | 8 / 4 | |
| 6.2.1 | 8 / 4 | |
| 6.2.0 | 8 / 4 | |
| 6.1.2 | 8 / 4 | |
| 6.1.1 | 8 / 4 | |
| 6.1.0 | 8 / 4 | |
| 6.0.0 | 9 / 5 | |
| 5.5.0 | 8 / 4 | |
| 5.4.0 | 8 / 4 | |
| 5.3.1 | 8 / 4 | |
| 5.3.0 | 8 / 4 | |
| 5.2.0 | 8 / 4 | |
| 5.1.0 | 8 / 4 | |
| 5.0.1 | 8 / 4 | |
| 5.0.0 | 8 / 4 | |
| 4.3.3 | 8 / 4 | |
| 4.3.2 | 8 / 4 | |
| 4.3.1 | 8 / 4 | |
| 4.3.0 | 8 / 4 | |
| 4.2.0 | 8 / 4 | |
| 4.1.0 | 8 / 4 | |
| 4.0.4 | 8 / 4 | |
| 4.0.3 | 8 / 4 | |
| 4.0.2 | 8 / 4 | |
| 4.0.1 | 8 / 4 | |
| 4.0.0 | 8 / 4 | |
| 3.1.0 | 6 / 4 | |
| 3.0.0 | 6 / 4 | |
| 2.4.1 | 6 / 4 | |
| 2.4.0 | 6 / 4 | |
| 2.3.0 | 6 / 4 | |
| 2.2.1 | 7 / 4 | |
| 2.2.0 | 7 / 4 | |
| 2.1.1 | 7 / 4 | |
| 2.1.0 | 7 / 4 | |
| 2.0.0 | 7 / 3 |
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v3.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.
v3.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.
v2.4.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.
v2.4.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.