@svgr/plugin-svgo
Optimize SVG
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:svgo | AI (dependencies): svgo is the canonical SVG optimizer and the core dependency this plugin is built around; its use is expected and stable across all versions of this package. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): deepmerge is explicitly declared as a runtime dependency in package.json; the phantom-dep finding is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Official SVGR monorepo package by the original author; lack of provenance attestation is not a meaningful risk signal here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 8.1.0 | 3 / 1 | |
| 8.0.1 | 3 / 1 | |
| 8.0.0 | 3 / 1 | |
| 7.0.0 | 3 / 0 | |
| 6.5.1 | 3 / 0 | |
| 6.5.0 | 3 / 0 | |
| 6.3.1 | 3 / 0 | |
| 6.3.0 | 3 / 0 | |
| 6.2.0 | 3 / 0 | |
| 6.1.2 | 3 / 0 | |
| 6.1.0 | 3 / 0 | |
| 6.0.0 | 3 / 0 | |
| 5.5.0 | 3 / 0 | |
| 5.4.0 | 3 / 0 | |
| 5.3.0 | 3 / 0 | |
| 5.2.0 | 3 / 0 | |
| 5.1.0 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.3.1 | 3 / 0 | |
| 4.2.0 | 3 / 0 | |
| 4.0.3 | 3 / 0 | |
| 4.0.0 | 3 / 0 |
v8.0.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.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.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.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.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.1
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.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.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.