@wordpress/priority-queue
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:requestidlecallback | AI (dependencies): requestidlecallback is a standard browser API polyfill; appropriate and expected for this priority-queue package. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 3.51.0 | 1 / 1 | |
| 3.50.0 | 1 / 1 | |
| 3.49.0 | 1 / 1 | |
| 3.48.1 | 1 / 1 | |
| 3.48.0 | 1 / 1 | |
| 3.47.0 | 1 / 1 | |
| 3.46.0 | 1 / 1 | |
| 3.45.0 | 1 / 1 | |
| 3.44.0 | 1 / 1 | |
| 3.43.0 | 1 / 1 | |
| 3.42.0 | 1 / 1 | |
| 3.41.0 | 1 / 1 | |
| 3.40.1 | 1 / 1 | |
| 3.40.0 | 1 / 1 | |
| 3.39.0 | 1 / 1 | |
| 3.38.0 | 1 / 1 | |
| 3.37.0 | 1 / 0 | |
| 3.36.0 | 1 / 0 | |
| 3.35.0 | 1 / 0 | |
| 3.34.0 | 1 / 0 | |
| 3.33.1 | 1 / 0 | |
| 3.33.0 | 1 / 0 | |
| 3.32.0 | 2 / 0 | |
| 3.31.0 | 2 / 0 | |
| 3.30.0 | 2 / 0 | |
| 3.29.0 | 2 / 0 | |
| 3.28.0 | 2 / 0 | |
| 3.27.0 | 2 / 0 | |
| 3.26.0 | 2 / 0 | |
| 3.25.0 | 2 / 0 | |
| 3.24.0 | 2 / 0 | |
| 3.23.0 | 2 / 0 | |
| 3.22.0 | 2 / 0 | |
| 3.21.0 | 2 / 0 | |
| 3.20.0 | 2 / 0 | |
| 3.19.1 | 2 / 0 | |
| 3.19.0 | 2 / 0 | |
| 3.18.0 | 2 / 0 | |
| 3.17.0 | 2 / 0 | |
| 3.16.0 | 2 / 0 | |
| 3.15.0 | 2 / 0 | |
| 3.14.0 | 2 / 0 | |
| 3.13.0 | 2 / 0 | |
| 3.12.0 | 2 / 0 | |
| 3.11.0 | 2 / 0 | |
| 3.10.0 | 2 / 0 | |
| 3.9.0 | 2 / 0 | |
| 3.8.1 | 2 / 0 | |
| 3.8.0 | 2 / 0 | |
| 3.7.0 | 2 / 0 | |
| 3.6.0 | 2 / 0 | |
| 3.5.0 | 2 / 0 | |
| 3.4.0 | 2 / 0 | |
| 3.3.0 | 2 / 0 | |
| 3.2.0 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 |
v3.51.0
2 findingsPackage 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.
v3.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.1
2 findingsPackage 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.
v3.22.0
2 findingsPackage 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.
v3.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-01-15, but gutenbergplugin 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.
v3.15.0
2 findingsPackage 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.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.