← Home

babel-plugin-transform-amd-system-wrapper

npm Repository Homepage

Wraps AMD scripts into System.registerDynamic(...

11
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

guybedfordjrauschenbusch

Keywords

babelpluginsystemjsbabel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change to guybedford (highly trusted npm publisher, 1828 approved packages) occurred in 2017 and is a legitimate historical maintainer transition for this package. ai
maintainer-change maintainer-added AI (maintainer-change): guybedford is a well-established, trusted npm publisher; this maintainer addition in 2017 reflects a legitimate transfer, not a compromise. ai

Versions (showing 11 of 11)

Version Deps Published
0.3.7 1 / 7
0.3.6 1 / 7
0.3.5 1 / 7
0.3.4 1 / 7
0.3.3 1 / 7
0.3.2 1 / 7
0.3.1 1 / 7
0.3.0 1 / 7
0.1.1 1 / 7
0.1.0 1 / 7
0.0.1 1 / 7

v0.3.7

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

1 finding
LOW No provenance attestation provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jrauschenbusch → guybedford (on 2017-01-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-01-24. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.2

2 findings
HIGH Publisher changed: jrauschenbusch → guybedford (on 2017-01-24) provenance

This version was published by a different npm account than previous versions on 2017-01-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.3.1

2 findings
HIGH Publisher changed: jrauschenbusch → guybedford (on 2017-01-24) provenance

This version was published by a different npm account than previous versions on 2017-01-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.3.0

2 findings
HIGH Publisher changed: jrauschenbusch → guybedford (on 2017-01-24) provenance

This version was published by a different npm account than previous versions on 2017-01-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

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