@livestore/common
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; description omission is cosmetic, not malicious. | ai | |
| dependencies | unvetted-dep:@livestore/db-schema | AI (dependencies): Internal sibling package in the same monorepo/org. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): Common in TS libs referenced only in config/type contexts. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo internal package; missing metadata is expected, not a spam/malware signal. | ai | |
| dependencies | unvetted-dep:@livestore/utils | AI (dependencies): Sibling monorepo package at matching version; consistent with legitimate monorepo release. | ai | |
| dependencies | unvetted-dep:@livestore/webmesh | AI (dependencies): Sibling monorepo package at matching version; consistent with legitimate monorepo release. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 3 / 21 | |
| 0.3.1 | 6 / 2 | |
| 0.3.0 | 6 / 2 | |
| 0.2.0 | 6 / 1 | |
| 0.1.0 | 6 / 1 | |
| 0.0.57 | 3 / 1 | |
| 0.0.56 | 3 / 1 | |
| 0.0.55 | 3 / 1 | |
| 0.0.54 | 3 / 1 | |
| 0.0.53 | 3 / 1 | |
| 0.0.52 | 3 / 1 | |
| 0.0.51 | 3 / 1 | |
| 0.0.50 | 3 / 1 | |
| 0.0.49 | 3 / 1 | |
| 0.0.48 | 3 / 1 | |
| 0.0.47 | 3 / 1 | |
| 0.0.46 | 3 / 1 | |
| 0.0.45 | 3 / 1 | |
| 0.0.44 | 3 / 1 | |
| 0.0.43 | 3 / 1 | |
| 0.0.42 | 3 / 1 |
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.