← Home

@svgr/babel-preset

SVGR preset that apply transformations from config

26
Versions
MIT
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

neoziro

Keywords

babel-pluginbabel-preset

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@svgr/babel-plugin-replace-jsx-attribute-value AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
dependencies unvetted-dep:@svgr/babel-plugin-add-jsx-attribute AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
dependencies unvetted-dep:@svgr/babel-plugin-svg-dynamic-title AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
dependencies unvetted-dep:@svgr/babel-plugin-svg-em-dimensions AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
dependencies unvetted-dep:@svgr/babel-plugin-remove-jsx-attribute AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
dependencies unvetted-dep:@svgr/babel-plugin-transform-svg-component AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
dependencies unvetted-dep:@svgr/babel-plugin-transform-react-native-svg AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
dependencies unvetted-dep:@svgr/babel-plugin-remove-jsx-empty-expression AI (dependencies): First-party sibling package from the same @svgr monorepo; not a third-party risk. ai
provenance no-provenance AI (provenance): SVGR is a well-established project with a clean publisher history; lack of Sigstore provenance is common and not a meaningful risk signal here. ai

Versions (showing 26 of 26)

Version Deps Published
8.1.0 8 / 0
8.0.0 8 / 0
7.0.0 8 / 0
6.5.1 8 / 0
6.5.0 8 / 0
6.4.0 8 / 0
6.3.1 8 / 0
6.3.0 8 / 0
6.2.0 8 / 0
6.1.0 8 / 0
6.0.0 8 / 0
5.5.0 8 / 0
5.4.0 8 / 0
5.3.1 8 / 0
5.3.0 8 / 0
5.2.0 8 / 0
5.0.1 8 / 0
5.0.0 8 / 0
4.3.3 8 / 0
4.3.1 8 / 0
4.3.0 8 / 0
4.2.0 8 / 0
4.1.0 8 / 0
4.0.3 8 / 0
4.0.1 8 / 0
4.0.0 8 / 0

v6.5.1

1 finding
INFO No provenance attestation provenance

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

v6.5.0

1 finding
INFO No provenance attestation provenance

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

v6.4.0

1 finding
INFO No provenance attestation provenance

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

v6.3.1

1 finding
INFO No provenance attestation provenance

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

v6.3.0

1 finding
INFO No provenance attestation provenance

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

v6.2.0

1 finding
INFO No provenance attestation provenance

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

v6.1.0

1 finding
INFO No provenance attestation provenance

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

v6.0.0

1 finding
INFO No provenance attestation provenance

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

v5.5.0

1 finding
INFO No provenance attestation provenance

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

v5.4.0

1 finding
INFO No provenance attestation provenance

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

v5.3.1

1 finding
INFO No provenance attestation provenance

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

v5.3.0

1 finding
INFO No provenance attestation provenance

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

v5.2.0

1 finding
INFO No provenance attestation provenance

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

v5.0.1

1 finding
INFO No provenance attestation provenance

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

v5.0.0

1 finding
INFO No provenance attestation provenance

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

v4.3.3

1 finding
INFO No provenance attestation provenance

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

v4.3.1

1 finding
INFO No provenance attestation provenance

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

v4.3.0

1 finding
INFO No provenance attestation provenance

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

v4.2.0

1 finding
INFO No provenance attestation provenance

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

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

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

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

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