← Home

babel-plugin-flow-comments

Turn flow type annotations into comments

8
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): sebmck→amasad is the documented Babel project maintainer transition in 2015; not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): amasad, jmm, loganfsmyth, thejameskyle are all known Babel core team members added during the 2015 project transition. ai
provenance missing-githead AI (provenance): 2015-era publish; gitHead absence is expected for this vintage and not indicative of tampering. ai
provenance no-provenance AI (provenance): Sigstore provenance did not exist in 2015; not applicable to this package version. ai
publish-pattern new-deps-added AI (publish-pattern): babel-runtime and babel-plugin-syntax-flow are standard Babel ecosystem packages; consistent with plugin functionality. ai
phantom-deps phantom-dep:babel-runtime AI (phantom-deps): babel-runtime is commonly used via Babel transforms without explicit imports; stable false positive for Babel plugins. ai

Versions (showing 8 of 8)

Version Deps Published
6.3.19 2 / 1
1.0.9 0 / 2
1.0.7 0 / 2
1.0.6 0 / 2
1.0.5 0 / 2
1.0.4 0 / 2
1.0.3 0 / 2
1.0.1 0 / 1

v6.3.19

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: amasad.

HIGH Publisher changed: sebmck → amasad (on 2015-12-14) provenance

This version was published by a different npm account than previous versions on 2015-12-14. 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.