babel-plugin-transform-decorators-legacy
A plugin for Babel 6 that (mostly) replicates the old decorator behavior from Babel 5.
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): This is a legitimate, decade-old Babel plugin by a known Babel contributor. The 0.0.0 version is the historical initial release, not a malicious throwaway package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from ide to loganfsmyth occurred in 2015; loganfsmyth is the documented author of this plugin and the GitHub repo is under his account. Historical, not a compromise signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): loganfsmyth is the canonical maintainer of this package; the maintainer addition is a legitimate historical transition, not a takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): loganfsmyth maintains a large Babel plugin ecosystem; mass-production signal reflects legitimate templated Babel plugin naming. README/keywords issues are cosmetic and not security-relevant. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is a standard Babel 6 runtime dependency used via transform-runtime; its indirect usage pattern is expected and not a security concern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.3.5 | 3 / 6 | |
| 1.3.4 | 3 / 6 | |
| 1.3.3 | 3 / 6 | |
| 1.3.2 | 3 / 6 | |
| 1.3.1 | 3 / 6 | |
| 1.3.0 | 3 / 6 | |
| 1.2.0 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.0 | 3 / 6 | |
| 0.0.0 | 3 / 3 |
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2015-12-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2015-12-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.