← Home

babel-plugin-syntax-flow

Allow parsing of the flow syntax

15
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

amasadhzoojmmloganfsmythsebmckthejameskyle

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Known Babel maintainer transition from sebmck to hzoo; stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): hzoo, jmm, loganfsmyth are established Babel core maintainers. ai

Versions (showing 15 of 15)

Version Deps Published
6.18.0 0 / 0
6.13.0 0 / 0
6.8.0 1 / 1
6.5.0 1 / 1
6.3.13 1 / 1
6.2.4 1 / 1
6.1.18 1 / 1
6.1.17 1 / 1
6.1.16 1 / 1
6.1.13 1 / 1
6.1.10 1 / 1
6.1.8 1 / 1
6.1.5 1 / 1
6.1.4 1 / 1
6.0.14 1 / 0

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: sebmck → hzoo (on 2016-05-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-05-02. This could indicate a legitimate maintainer transition or an account compromise.

v6.5.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

[Accepted risk] 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.

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.