← Home

lib0

npm Repository Homepage

> Monorepo of isomorphic utility functions

13
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dmonad

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/testing.cjs AI (source-diff): Base64-encoded Nyan Cat GIF used as test fixture; stable across versions. ai
publish-pattern dormant-publish AI (publish-pattern): Trusted maintainer (dmonad/yjs ecosystem) resumed publishing; not indicative of takeover. ai
semgrep semgrep:base64-decode AI (semgrep): lib0 is a binary/encoding utility library; Buffer.from(s, 'base64') is core functionality, not obfuscation. ai

Versions (showing 13 of 13)

Version Deps Published
0.2.117 1 / 7
0.2.116 1 / 7
0.2.115 1 / 7
0.2.114 1 / 7
0.2.112 1 / 7
0.2.111 1 / 7
0.2.110 1 / 7
0.2.109 1 / 7
0.2.108 1 / 7
0.2.107 1 / 7
0.2.106 1 / 7
0.2.105 1 / 7
0.2.99 1 / 7

v0.2.116

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.115

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.114

2 findings
HIGH Long encoded string in modified file: dist/testing.cjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.112

2 findings
HIGH Long encoded string in modified file: dist/testing.cjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.111

2 findings
HIGH Long encoded string in modified file: dist/testing.cjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.110

2 findings
HIGH Long encoded string in modified file: dist/testing.cjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.109

2 findings
HIGH Long encoded string in modified file: dist/testing.cjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.108

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.107

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.106

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.105

2 findings
HIGH Long encoded string in modified file: dist/testing.cjs source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.99

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.