@svgr/core
Transform SVG into React Components.
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:merge-deep | AI (dependencies): merge-deep is a well-known, legitimate deep-merge utility; its use in @svgr/core for config merging is appropriate and poses no security risk. | ai | |
| dependencies | unvetted-dep:svgo | AI (dependencies): svgo is a well-known, widely-used SVG optimizer; its use here is expected and legitimate for this SVG-to-React toolchain. | ai | |
| dependencies | unvetted-dep:h2x-core | AI (dependencies): h2x-core is a core dependency of the SVGR ecosystem, authored by the same maintainer (neoziro); legitimate and expected. | ai | |
| dependencies | unvetted-dep:h2x-plugin-jsx | AI (dependencies): h2x-plugin-jsx is a core dependency of the SVGR ecosystem, authored by the same maintainer (neoziro); legitimate and expected. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm by years; absence is expected and not a risk signal for this well-established package. | ai | |
| phantom-deps | phantom-dep:output-file-sync | AI (phantom-deps): Monorepo structure; deps declared at package level but used by sibling packages. Not a security concern. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Monorepo structure; deps declared at package level but used by sibling packages (CLI). Not a security concern. | ai | |
| phantom-deps | phantom-dep:loader-utils | AI (phantom-deps): Monorepo structure; deps declared at package level but used by sibling packages (webpack loader). Not a security concern. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Monorepo structure; deps declared at package level but used by sibling packages. Not a security concern. | ai | |
| phantom-deps | phantom-dep:recursive-readdir | AI (phantom-deps): Monorepo structure; deps declared at package level but used by sibling packages. Not a security concern. | ai | |
| phantom-deps | phantom-dep:mz | AI (phantom-deps): Monorepo structure; deps declared at package level but used by sibling packages (CLI, loader). Not a security concern. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @svgr/core is a scoped package in the svgr ecosystem; the levenshtein match to 'cors' is coincidental and not a typosquat. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 8.1.0 | 5 / 1 | |
| 8.0.0 | 5 / 1 | |
| 7.0.0 | 4 / 0 | |
| 6.5.1 | 5 / 1 | |
| 6.5.0 | 5 / 1 | |
| 6.4.0 | 4 / 1 | |
| 6.3.1 | 3 / 1 | |
| 6.3.0 | 3 / 1 | |
| 6.2.1 | 3 / 1 | |
| 6.2.0 | 3 / 1 | |
| 6.1.2 | 3 / 1 | |
| 6.1.1 | 3 / 1 | |
| 6.1.0 | 3 / 1 | |
| 6.0.0 | 3 / 1 | |
| 5.5.0 | 3 / 0 | |
| 5.4.0 | 3 / 0 | |
| 5.3.1 | 3 / 0 | |
| 5.3.0 | 3 / 0 | |
| 5.2.0 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.3.3 | 3 / 0 | |
| 4.3.2 | 3 / 0 | |
| 4.3.1 | 3 / 0 | |
| 4.3.0 | 3 / 0 | |
| 4.2.0 | 3 / 0 | |
| 4.1.0 | 3 / 0 | |
| 4.0.3 | 3 / 0 | |
| 4.0.2 | 3 / 0 | |
| 4.0.1 | 3 / 0 | |
| 4.0.0 | 3 / 0 | |
| 3.1.0 | 7 / 0 | |
| 3.0.0 | 7 / 0 | |
| 2.4.1 | 7 / 0 | |
| 2.4.0 | 7 / 0 | |
| 2.2.0 | 6 / 0 | |
| 2.1.1 | 6 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.0 | 12 / 0 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
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.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.