workbox-window MIT 39 versions

workbox-window

npm Repository Homepage

Simplifies communications with Workbox packages running in the service worker

39

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 workerswwindowmessagepostMessage

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition between Google DevRel team members (tropicadri → tomayac). tomayac has strong npm track record (775 approved packages).	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): tomayac is a known Google Developer Advocate; addition reflects normal Google team rotation.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): snugug removal is part of normal Google team rotation on the Workbox project.	ai	2026/04/24
phantom-deps	phantom-dep:@types/trusted-types	AI (phantom-deps): TypeScript type declaration dependency; used for type-checking, not direct runtime import.	ai	2026/04/24

Versions (showing 39 of 39)

Version	Deps	Published
7.4.1	2 / 0	2026-05-04
7.4.0	2 / 0	2025-11-19
7.3.0	2 / 0	2024-10-29
7.1.0	2 / 0	2024-04-23
7.0.0	2 / 0	2023-05-31
6.6.1	2 / 0	2023-05-30
6.6.0	2 / 0	2023-05-26
6.5.4	2 / 0	2022-07-27
6.5.3	2 / 0	2022-04-12
6.5.2	2 / 0	2022-03-24
6.5.1	2 / 0	2022-03-03
6.5.0	2 / 0	2022-02-23
6.4.2	2 / 0	2021-12-02
6.4.1	2 / 0	2021-11-15
6.4.0	2 / 0	2021-11-03
6.3.0	2 / 0	2021-09-09
6.2.4	2 / 0	2021-08-11
6.2.3	2 / 0	2021-08-10
6.2.2	1 / 1	2021-08-06
6.2.1	1 / 1	2021-08-06
6.2.0	1 / 1	2021-08-05
6.1.5	1 / 0	2021-04-12
6.1.2	1 / 0	2021-03-15
6.1.1	1 / 0	2021-02-22
6.1.0	1 / 0	2021-01-29
6.0.2	1 / 0	2020-12-03
6.0.0	1 / 0	2020-11-30
5.1.4	1 / 0	2020-09-09
5.1.3	1 / 0	2020-04-24
5.1.2	1 / 0	2020-03-25
5.1.1	1 / 0	2020-03-19
5.1.0	1 / 0	2020-03-19
5.0.0	1 / 0	2020-01-29
4.3.1	1 / 0	2019-05-01
4.3.0	1 / 0	2019-04-15
4.2.0	1 / 0	2019-04-03
4.1.1	1 / 0	2019-03-15
4.1.0	1 / 0	2019-03-07
4.0.0	1 / 0	2019-02-27

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

1 finding

LOW No provenance attestation provenance

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

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.