@wordpress/viewport
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@wordpress/element | AI (phantom-deps): @wordpress/element is a declared dependency in package.json; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Gutenberg monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 6.51.0 | 3 / 3 | |
| 6.50.0 | 3 / 3 | |
| 6.49.0 | 3 / 3 | |
| 6.48.1 | 4 / 3 | |
| 6.48.0 | 3 / 1 | |
| 6.47.0 | 3 / 1 | |
| 6.46.0 | 3 / 1 | |
| 6.45.0 | 3 / 1 | |
| 6.44.0 | 3 / 1 | |
| 6.43.0 | 3 / 1 | |
| 6.42.0 | 3 / 1 | |
| 6.41.0 | 3 / 1 | |
| 6.40.1 | 3 / 1 | |
| 6.40.0 | 3 / 1 | |
| 6.39.0 | 3 / 1 | |
| 6.38.0 | 3 / 1 | |
| 6.37.0 | 3 / 0 | |
| 6.36.0 | 3 / 0 | |
| 6.35.0 | 3 / 0 | |
| 6.34.0 | 3 / 0 | |
| 6.33.1 | 3 / 0 | |
| 6.33.0 | 3 / 0 | |
| 6.32.0 | 4 / 0 | |
| 6.31.0 | 4 / 0 | |
| 6.30.0 | 4 / 0 | |
| 6.29.0 | 4 / 0 | |
| 6.28.0 | 4 / 0 | |
| 6.27.0 | 4 / 0 | |
| 6.26.0 | 4 / 0 | |
| 6.25.0 | 4 / 0 | |
| 6.24.0 | 4 / 0 | |
| 6.23.0 | 4 / 0 | |
| 6.22.0 | 4 / 0 | |
| 6.21.0 | 4 / 0 | |
| 6.20.0 | 4 / 0 | |
| 6.19.2 | 4 / 0 | |
| 6.19.1 | 4 / 0 | |
| 6.19.0 | 4 / 0 | |
| 6.18.0 | 4 / 0 | |
| 6.17.0 | 4 / 0 | |
| 6.16.0 | 4 / 0 | |
| 6.15.1 | 4 / 0 | |
| 6.15.0 | 4 / 0 | |
| 6.14.0 | 4 / 0 | |
| 6.13.0 | 4 / 0 | |
| 6.12.0 | 4 / 0 | |
| 6.11.0 | 4 / 0 | |
| 6.10.0 | 4 / 0 | |
| 6.9.0 | 4 / 0 | |
| 6.8.4 | 4 / 0 | |
| 6.8.3 | 4 / 0 |
v6.51.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-07-14, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.40.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-06-30, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.22.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-04-11, but gziolo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-01-03, but gziolo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.