@xyo-network/previous-hash-store
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Large monorepo with frequent releases; publish environment change is plausible and no other risk signals present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Package explicitly re-exports from @xyo-network/sdk-protocol; the new dep is the stated purpose of this stub. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Barrel/re-export package in @xyo-network monorepo; low README and no keywords are normal for internal SDK modules. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large established XYO monorepo; dormancy consistent with development pause, not takeover. | ai | |
| dependencies | unvetted-dep:@xyo-network/previous-hash-store-storage | AI (dependencies): Same-org sibling package from xyo-network monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@xyo-network/previous-hash-store-indexeddb | AI (dependencies): Same-org sibling package from xyo-network monorepo; stable pattern across versions. | ai |
Versions (showing 51 of 110)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 1 / 23 | |
| 7.0.14 | 3 / 12 | |
| 7.0.13 | 3 / 13 | |
| 7.0.12 | 1 / 6 | |
| 7.0.11 | 1 / 6 | |
| 7.0.10 | 1 / 6 | |
| 7.0.9 | 1 / 6 | |
| 7.0.8 | 1 / 6 | |
| 7.0.7 | 1 / 6 | |
| 7.0.6 | 1 / 6 | |
| 7.0.5 | 3 / 17 | |
| 7.0.4 | 3 / 17 | |
| 7.0.3 | 3 / 15 | |
| 7.0.2 | 3 / 15 | |
| 7.0.0 | 3 / 15 | |
| 6.1.1 | 3 / 15 | |
| 6.1.0 | 3 / 15 | |
| 6.0.9 | 3 / 18 | |
| 6.0.8 | 3 / 19 | |
| 6.0.7 | 3 / 18 | |
| 6.0.6 | 3 / 18 | |
| 6.0.5 | 3 / 19 | |
| 6.0.4 | 3 / 20 | |
| 6.0.3 | 3 / 20 | |
| 6.0.2 | 3 / 20 | |
| 6.0.1 | 3 / 20 | |
| 6.0.0 | 3 / 20 | |
| 5.6.3 | 3 / 20 | |
| 5.6.2 | 3 / 20 | |
| 5.5.2 | 3 / 22 | |
| 5.5.1 | 3 / 22 | |
| 5.5.0 | 3 / 42 | |
| 5.4.1 | 3 / 15 | |
| 5.4.0 | 3 / 15 | |
| 5.3.30 | 3 / 17 | |
| 5.3.29 | 3 / 17 | |
| 5.3.27 | 3 / 19 | |
| 5.3.26 | 3 / 20 | |
| 5.3.25 | 3 / 20 | |
| 5.3.24 | 3 / 20 | |
| 5.3.22 | 3 / 20 | |
| 5.3.20 | 3 / 11 | |
| 5.3.17 | 3 / 10 | |
| 5.3.16 | 3 / 10 | |
| 5.3.15 | 3 / 5 | |
| 5.3.13 | 3 / 5 | |
| 5.3.12 | 3 / 5 | |
| 5.3.11 | 3 / 5 | |
| 5.3.10 | 3 / 5 | |
| 5.3.8 | 3 / 5 | |
| 5.3.7 | 3 / 5 |
v7.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.30
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.29
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.27
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.26
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.25
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.24
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.20
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 (jonesmac) than the most recent previously approved version (xyo) on 2026-03-30, but jonesmac 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.