← Home

@next/polyfill-nomodule

A polyfill for non-dead, nomodule browsers.

51
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

vercel-release-botmatt.straka

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence reflects CI pipeline change, not a supply chain risk for this Vercel package. ai
maintainer-change maintainer-removed AI (maintainer-change): Vercel org manages Next.js; maintainer roster changes are routine org-level decisions, not takeover signals. ai
provenance publisher-changed AI (provenance): Vercel migrated releases to GitHub Actions with SLSA attestation; this is a legitimate infra change, not a takeover. ai

Versions (showing 51 of 70)

View all versions
Version Deps Published
16.2.12 0 / 4
16.2.11 0 / 4
16.2.10 0 / 4
16.2.9 0 / 4
16.2.8 0 / 4
16.2.7 0 / 4
16.2.6 0 / 4
16.2.5 0 / 4
16.2.4 0 / 4
16.2.3 0 / 4
16.2.2 0 / 4
16.2.1 0 / 4
16.2.0 0 / 4
16.1.7 0 / 4
16.1.6 0 / 4
16.1.5 0 / 4
16.1.4 0 / 4
16.1.3 0 / 4
16.1.2 0 / 4
16.1.1 0 / 4
16.1.0 0 / 4
16.0.11 0 / 4
16.0.10 0 / 4
16.0.9 0 / 4
16.0.8 0 / 4
16.0.7 0 / 4
16.0.6 0 / 4
16.0.5 0 / 4
16.0.4 0 / 4
16.0.3 0 / 4
16.0.2 0 / 4
16.0.1 0 / 4
16.0.0 0 / 4
15.5.22 0 / 4
15.5.21 0 / 4
15.5.20 0 / 4
15.5.19 0 / 4
15.5.18 0 / 4
15.5.16 0 / 4
15.5.15 0 / 4
15.5.14 0 / 4
15.5.13 0 / 4
15.5.12 0 / 4
15.5.11 0 / 4
15.5.10 0 / 4
15.5.9 0 / 4
15.5.8 0 / 4
15.5.7 0 / 4
15.4.11 0 / 4
15.4.10 0 / 4
15.4.9 0 / 4

v16.2.12

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.

v16.2.11

2 findings
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.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v16.2.10

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: GitHub Actions.

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.

v15.5.22

2 findings
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.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v15.5.21

2 findings
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.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v15.5.20

2 findings
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.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.