@wordpress/undo-manager
A small package to manage undo/redo.
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 59)
| Version | Deps | Published |
|---|---|---|
| 1.51.0 | 1 / 1 | |
| 1.50.0 | 1 / 1 | |
| 1.49.0 | 1 / 1 | |
| 1.48.1 | 1 / 1 | |
| 1.48.0 | 1 / 1 | |
| 1.47.0 | 1 / 1 | |
| 1.46.0 | 1 / 1 | |
| 1.45.0 | 1 / 1 | |
| 1.44.0 | 1 / 1 | |
| 1.43.0 | 1 / 1 | |
| 1.42.0 | 1 / 1 | |
| 1.41.0 | 1 / 1 | |
| 1.40.1 | 1 / 1 | |
| 1.40.0 | 1 / 1 | |
| 1.39.0 | 1 / 1 | |
| 1.38.0 | 1 / 1 | |
| 1.37.0 | 1 / 0 | |
| 1.36.0 | 1 / 0 | |
| 1.35.0 | 1 / 0 | |
| 1.34.0 | 1 / 0 | |
| 1.33.1 | 1 / 0 | |
| 1.33.0 | 1 / 0 | |
| 1.32.0 | 2 / 0 | |
| 1.31.0 | 2 / 0 | |
| 1.30.0 | 2 / 0 | |
| 1.29.0 | 2 / 0 | |
| 1.28.0 | 2 / 0 | |
| 1.27.0 | 2 / 0 | |
| 1.26.0 | 2 / 0 | |
| 1.25.0 | 2 / 0 | |
| 1.24.0 | 2 / 0 | |
| 1.23.0 | 2 / 0 | |
| 1.22.0 | 2 / 0 | |
| 1.21.0 | 2 / 0 | |
| 1.20.0 | 2 / 0 | |
| 1.19.1 | 2 / 0 | |
| 1.19.0 | 2 / 0 | |
| 1.18.0 | 2 / 0 | |
| 1.17.0 | 2 / 0 | |
| 1.16.0 | 2 / 0 | |
| 1.15.1 | 2 / 0 | |
| 1.15.0 | 2 / 0 | |
| 1.14.0 | 2 / 0 | |
| 1.13.0 | 2 / 0 | |
| 1.12.0 | 2 / 0 | |
| 1.11.0 | 2 / 0 | |
| 1.10.0 | 2 / 0 | |
| 1.9.0 | 2 / 0 | |
| 1.8.1 | 2 / 0 | |
| 1.8.0 | 2 / 0 | |
| 1.7.0 | 2 / 0 |
v1.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.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.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.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.15.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 (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-01-03, 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.
v1.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.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.