← Home

@babel/plugin-syntax-function-sent

npm Repository Homepage

Allow parsing of the function.sent meta property

17
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hzooexistentialismnicolo-ribaudojlhwung

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from hzoo to nicolo-ribaudo reflects the documented Babel core team transition in 2019; nicolo-ribaudo is a known Babel maintainer with strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers developit and nicolo-ribaudo are known Babel ecosystem contributors; addition reflects legitimate team transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of xtuc is part of the documented 2019 Babel team restructuring, not a hostile takeover. ai
bogus-package bogus-package AI (bogus-package): Babel publishes hundreds of small, templated plugin packages by design. Tiny payload and mass-production signals are expected and benign for @babel/* packages. ai
provenance no-provenance AI (provenance): This package predates widespread Sigstore provenance adoption; absence of attestation is not a risk signal for established @babel/* packages. ai

Versions (showing 17 of 17)

Show 5 prereleases
Version Deps Published
7.29.7 1 / 1
7.28.6 1 / 1
7.27.1 1 / 1
7.25.9 1 / 1
7.25.7 1 / 1
7.24.7 1 / 1
7.24.6 1 / 1
7.22.5 1 / 1
7.14.5 1 / 1
7.12.13 1 / 1
7.10.4 1 / 1
7.10.1 1 / 1
7.8.3 1 / 1
7.8.0 1 / 1
7.7.4 1 / 1
7.2.0 1 / 1
7.0.0 1 / 1

v7.29.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v7.25.9

1 finding
LOW No provenance attestation provenance

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

v7.25.7

1 finding
LOW No provenance attestation provenance

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

v7.24.7

1 finding
LOW No provenance attestation provenance

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

v7.24.6

1 finding
LOW No provenance attestation provenance

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

v7.22.5

1 finding
LOW No provenance attestation provenance

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

v7.14.5

2 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: nicolo-ribaudo.

LOW No provenance attestation provenance

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

v7.12.13

2 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: nicolo-ribaudo.

LOW No provenance attestation provenance

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

v7.10.4

2 findings
HIGH Publisher changed: nicolo-ribaudo → jlhwung (on 2020-06-30) provenance

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

v7.10.1

1 finding
LOW No provenance attestation provenance

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

v7.8.3

1 finding
LOW No provenance attestation provenance

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

v7.8.0

2 findings
HIGH Publisher changed: hzoo → nicolo-ribaudo (on 2020-01-12) provenance

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

v7.7.4

2 findings
HIGH Publisher changed: hzoo → nicolo-ribaudo (on 2019-11-22) provenance

This version was published by a different npm account than previous versions on 2019-11-22. 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.

v7.2.0

2 findings
HIGH Publisher changed: hzoo → nicolo-ribaudo (on 2018-12-03) provenance

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

v7.0.0

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.