← Home

workbox-navigation-preload

This library allows developers to opt-in to using Navigation Preload in their service worker.

45
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

gauntfacejeffposnickaddyosmaniphilipwaltontropicadriwestonrutertomayackhempeniusswissspidy

Keywords

workboxworkboxjsservice workerswnavigation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): tomayac (Thomas Steiner) is a Google DevRel engineer on the Workbox team; legitimate maintainer transition within the same project. ai
maintainer-change maintainer-added AI (maintainer-change): tomayac is a known Google DevRel team member; addition is a legitimate team rotation for the Workbox project. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of snugug alongside addition of tomayac reflects normal Google team rotation on the Workbox project. ai
publish-pattern dormant-publish AI (publish-pattern): Workbox is a mature, stable library; gaps between releases are normal and expected. ai

Versions (showing 45 of 45)

Version Deps Published
7.4.1 1 / 0
7.4.0 1 / 0
7.3.0 1 / 0
7.1.0 1 / 0
7.0.0 1 / 0
6.6.1 1 / 0
6.6.0 1 / 0
6.5.4 1 / 0
6.5.3 1 / 0
6.5.2 1 / 0
6.5.1 1 / 0
6.5.0 1 / 0
6.4.2 1 / 0
6.4.1 1 / 0
6.4.0 1 / 0
6.3.0 1 / 0
6.2.4 1 / 0
6.2.3 1 / 0
6.2.2 1 / 0
6.2.1 1 / 0
6.2.0 1 / 0
6.1.5 1 / 0
6.1.2 1 / 0
6.1.1 1 / 0
6.1.0 1 / 0
6.0.2 1 / 0
6.0.0 1 / 0
5.1.4 1 / 0
5.1.3 1 / 0
5.1.2 1 / 0
5.1.1 1 / 0
5.1.0 1 / 0
5.0.0 1 / 0
4.3.1 1 / 0
4.3.0 1 / 0
4.2.0 1 / 0
4.1.1 1 / 0
4.1.0 1 / 0
4.0.0 1 / 0
3.6.3 1 / 0
3.6.2 1 / 0
3.6.1 1 / 0
3.5.0 1 / 0
3.4.1 1 / 0
1.0.0 0 / 0

v7.4.1

1 finding
LOW No provenance attestation provenance

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

v7.3.0

2 findings
HIGH Publisher changed: tropicadri → tomayac (on 2024-10-29) provenance

This version was published by a different npm account than previous versions on 2024-10-29. 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.1.0

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

v6.6.1

1 finding
LOW No provenance attestation provenance

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

v6.6.0

1 finding
LOW No provenance attestation provenance

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

v6.5.3

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: jeffposnick → tropicadri (on 2022-04-12) provenance

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

v6.5.2

1 finding
LOW No provenance attestation provenance

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

v6.5.1

1 finding
LOW No provenance attestation provenance

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

v6.5.0

1 finding
LOW No provenance attestation provenance

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

v6.4.2

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: tropicadri → jeffposnick (on 2021-12-02) provenance

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

v6.4.1

1 finding
LOW No provenance attestation provenance

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

v6.4.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: jeffposnick → tropicadri (on 2021-11-03) provenance

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

v6.3.0

1 finding
LOW No provenance attestation provenance

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

v6.2.4

1 finding
LOW No provenance attestation provenance

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

v6.2.3

1 finding
LOW No provenance attestation provenance

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

v6.2.2

1 finding
LOW No provenance attestation provenance

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

v6.2.1

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: tropicadri → jeffposnick (on 2021-08-06) provenance

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

v6.2.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: tropicadri → jeffposnick (on 2021-08-05) provenance

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

v6.1.5

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: jeffposnick → tropicadri (on 2021-04-12) provenance

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

v6.1.2

1 finding
LOW No provenance attestation provenance

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

v6.1.1

1 finding
LOW No provenance attestation provenance

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

v6.1.0

1 finding
LOW No provenance attestation provenance

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

v6.0.2

1 finding
LOW No provenance attestation provenance

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

v6.0.0

1 finding
LOW No provenance attestation provenance

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