gui-chat-protocol
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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 13 | |
| 1.1.0 | 0 / 13 | |
| 1.0.0 | 0 / 13 | |
| 0.4.0 | 0 / 6 | |
| 0.3.3 | 0 / 6 | |
| 0.2.0 | 0 / 6 | |
| 0.1.0 | 0 / 6 | |
| 0.0.4 | 0 / 6 | |
| 0.0.3 | 0 / 6 | |
| 0.0.2 | 0 / 6 | |
| 0.0.1 | 0 / 6 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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 (isamu) than the most recent previously approved version (snakajima) on 2026-07-21, but isamu 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.