@wordpress/html-entities
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
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 4.51.0 | 0 / 0 | |
| 4.50.0 | 0 / 0 | |
| 4.49.0 | 0 / 0 | |
| 4.48.1 | 0 / 0 | |
| 4.48.0 | 0 / 0 | |
| 4.47.0 | 0 / 0 | |
| 4.46.0 | 0 / 0 | |
| 4.45.0 | 0 / 0 | |
| 4.44.0 | 0 / 0 | |
| 4.43.0 | 0 / 0 | |
| 4.42.0 | 0 / 0 | |
| 4.41.0 | 0 / 0 | |
| 4.40.1 | 0 / 0 | |
| 4.40.0 | 0 / 0 | |
| 4.39.0 | 0 / 0 | |
| 4.38.0 | 0 / 0 | |
| 4.37.0 | 0 / 0 | |
| 4.36.0 | 0 / 0 | |
| 4.35.0 | 0 / 0 | |
| 4.34.0 | 0 / 0 | |
| 4.33.1 | 0 / 0 | |
| 4.33.0 | 0 / 0 | |
| 4.32.0 | 1 / 0 | |
| 4.31.0 | 1 / 0 | |
| 4.30.0 | 1 / 0 | |
| 4.29.0 | 1 / 0 | |
| 4.28.0 | 1 / 0 | |
| 4.27.0 | 1 / 0 | |
| 4.26.0 | 1 / 0 | |
| 4.25.0 | 1 / 0 | |
| 4.24.0 | 1 / 0 | |
| 4.23.0 | 1 / 0 | |
| 4.22.0 | 1 / 0 | |
| 4.21.0 | 1 / 0 | |
| 4.20.0 | 1 / 0 | |
| 4.19.1 | 1 / 0 | |
| 4.19.0 | 1 / 0 | |
| 4.18.0 | 1 / 0 | |
| 4.17.0 | 1 / 0 | |
| 4.16.0 | 1 / 0 | |
| 4.15.0 | 1 / 0 | |
| 4.14.0 | 1 / 0 | |
| 4.13.0 | 1 / 0 | |
| 4.12.0 | 1 / 0 | |
| 4.11.0 | 1 / 0 | |
| 4.10.0 | 1 / 0 | |
| 4.9.0 | 1 / 0 | |
| 4.8.1 | 1 / 0 | |
| 4.8.0 | 1 / 0 | |
| 4.7.0 | 1 / 0 | |
| 4.6.0 | 1 / 0 |
v4.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.
v4.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.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.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.