← Home

babel-plugin-transform-decorators

npm Repository

Compile class and object decorators to ES5

18
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

amasadhzoojmmloganfsmythsebmckthejameskyle

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The sebmck→hzoo transition is the well-documented, publicly known Babel project maintainership handoff in early 2016. Legitimate transfer, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): hzoo, jmm, loganfsmyth are known Babel core team members added during the documented 2016 Babel project maintainership transition. ai
phantom-deps phantom-dep:babel-types AI (phantom-deps): babel-types is a legitimate declared dependency used by the Babel plugin ecosystem; not directly imported in main source but used transitively. ai
phantom-deps phantom-dep:babel-helper-define-map AI (phantom-deps): babel-helper-define-map is a legitimate declared dependency in the Babel plugin ecosystem; phantom-dep finding is a false positive for this package. ai

Versions (showing 18 of 18)

Version Deps Published
6.24.1 5 / 1
6.22.0 5 / 1
6.13.0 6 / 1
6.8.0 6 / 1
6.6.5 6 / 1
6.6.4 6 / 1
6.6.0 6 / 1
6.5.0 6 / 1
6.4.0 6 / 1
6.3.13 6 / 1
6.2.4 6 / 1
6.1.18 6 / 1
6.1.17 6 / 1
6.1.10 6 / 1
6.1.5 6 / 1
6.1.4 6 / 1
6.0.14 6 / 0
6.0.2 6 / 0

v6.24.1

1 finding
LOW No provenance attestation provenance

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

v6.22.0

1 finding
LOW No provenance attestation provenance

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

v6.13.0

1 finding
LOW No provenance attestation provenance

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

v6.8.0

1 finding
LOW No provenance attestation provenance

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

v6.6.5

1 finding
LOW No provenance attestation provenance

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

v6.6.4

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2016-03-02) provenance

This version was published by a different npm account than previous versions on 2016-03-02. 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.

v6.6.0

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2016-02-29) provenance

This version was published by a different npm account than previous versions on 2016-02-29. 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.

v6.5.0

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

This version was published by a different npm account than previous versions on 2016-02-07. 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.

v6.4.0

2 findings
HIGH Publisher changed: sebmck → hzoo (on 2016-01-06) provenance

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

v6.3.13

1 finding
LOW No provenance attestation provenance

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

v6.2.4

1 finding
LOW No provenance attestation provenance

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

v6.1.18

1 finding
LOW No provenance attestation provenance

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

v6.1.17

1 finding
LOW No provenance attestation provenance

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

v6.1.10

1 finding
LOW No provenance attestation provenance

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

v6.1.5

1 finding
LOW No provenance attestation provenance

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

v6.1.4

1 finding
LOW No provenance attestation provenance

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

v6.0.14

1 finding
LOW No provenance attestation provenance

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

v6.0.2

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.