babel-plugin-export-metadata
Add file metadata for function declarations
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package is 2652 days old with 62 versions; missing gitHead likely reflects a tooling change rather than a supply-chain compromise. No other corroborating malicious signals. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Older niche Babel plugin predating modern packaging conventions; has real inbound edges and long registry history. Missing repo/keywords/README code is cosmetic, not indicative of spam or malice. | ai | |
| phantom-deps | phantom-dep:@babel/cli | AI (phantom-deps): Framework-scoped Babel package declared as dependency but loaded by convention; normal for Babel plugins. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped Babel package declared as dependency but loaded by convention; normal for Babel plugins. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from rakannimer to renatobenks is a documented maintainer transition within the docz project; renatobenks has a strong track record (313 approved packages). | ai | |
| phantom-deps | phantom-dep:babel-core | AI (phantom-deps): babel-core 7.0.0-bridge.0 is the standard Babel 7 compatibility shim; referenced in config files by convention. | ai | |
| dependencies | unvetted-dep:babel-core | AI (dependencies): babel-core 7.0.0-bridge.0 is the well-known Babel 7 bridge shim, widely used across the ecosystem. | ai | |
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): Framework-scoped Babel package declared as dependency but loaded by convention; normal for Babel plugins. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): renatobenks is a legitimate docz maintainer with a strong track record; this is a stable transition, not a takeover. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 6 / 0 | |
| 2.3.0 | 6 / 4 | |
| 2.1.0 | 6 / 4 | |
| 2.0.0 | 6 / 4 | |
| 1.2.0 | 6 / 3 | |
| 1.1.0 | 6 / 3 | |
| 1.0.4 | 6 / 3 | |
| 1.0.2 | 6 / 3 | |
| 1.0.1 | 6 / 3 | |
| 1.0.0 | 6 / 2 | |
| 0.13.4 | 6 / 2 |
v2.4.0
2 findingsThis version was published by a different npm account than previous versions on 2022-02-11. 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.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rakannimer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.