partysocket
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Cloudflare/partykit migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate repo-based publish. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by Cloudflare org maintenance cadence; SLSA attestation confirms legitimate source. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 1 / 2 | |
| 1.2.0 | 1 / 2 | |
| 1.1.19 | 1 / 2 | |
| 1.1.18 | 1 / 2 | |
| 1.1.17 | 1 / 2 | |
| 1.1.16 | 1 / 2 | |
| 1.1.15 | 1 / 2 | |
| 1.1.14 | 1 / 2 | |
| 1.1.13 | 1 / 2 | |
| 1.1.12 | 1 / 2 | |
| 1.1.11 | 1 / 2 | |
| 1.1.10 | 1 / 1 | |
| 1.1.9 | 1 / 1 | |
| 1.1.8 | 1 / 1 | |
| 1.1.6 | 1 / 1 | |
| 1.1.5 | 1 / 1 | |
| 1.1.4 | 1 / 1 | |
| 1.1.3 | 1 / 1 | |
| 1.1.2 | 1 / 0 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 1 / 0 | |
| 1.0.3 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 |
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.