y-protocols
Yjs encoding protocols
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/test.js | AI (source-diff): Encoded string is a base64 nyan-cat GIF in the test reporter; stable benign artifact. | ai | |
| dependencies | unvetted-dep:lib0 | AI (dependencies): lib0 is a core Yjs ecosystem utility library authored by the same maintainer (dmonad); it is a well-known, legitimate dependency stable across all y-protocols versions. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is common (~88% of packages) and not a security risk for this well-established Yjs ecosystem package with a known publisher. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 1 / 8 | |
| 1.0.6 | 1 / 8 | |
| 1.0.5 | 1 / 7 | |
| 1.0.4 | 1 / 7 | |
| 1.0.3 | 1 / 7 | |
| 1.0.2 | 1 / 7 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 4 |
v1.0.5
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.