← Home

babel-plugin-transform-global-system-wrapper

npm Repository Homepage

Converts global scripts into named System.registerDynamic('name', [], ...

7
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

asapachguybedford

Keywords

babelpluginsystemjsbabel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): guybedford is the primary SystemJS maintainer; transfer from asapach to guybedford in 2017 is a legitimate handoff for this systemjs-org package. Generalizes across versions. ai
maintainer-change maintainer-added AI (maintainer-change): guybedford is the canonical SystemJS maintainer; addition is a legitimate transfer, not a compromise. Stable for this package. ai

Versions (showing 7 of 7)

Version Deps Published
0.3.4 1 / 7
0.3.2 1 / 7
0.3.1 1 / 7
0.3.0 1 / 7
0.2.0 1 / 7
0.1.0 1 / 7
0.0.1 1 / 7

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

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

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

2 findings
HIGH Publisher changed: asapach → guybedford (on 2017-01-23) provenance

This version was published by a different npm account than previous versions on 2017-01-23. 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.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.