@xyo-network/diviner-boundwitness-memory
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@xyo-network/diviner-boundwitness-model | AI (dependencies): Same-org monorepo sibling dep; versioned in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-boundwitness-abstract | AI (dependencies): Same-org monorepo sibling dep; versioned in lockstep with this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 5.4.0 | 4 / 41 | |
| 5.2.22 | 7 / 10 | |
| 5.2.20 | 7 / 10 | |
| 5.1.23 | 9 / 10 | |
| 5.1.22 | 9 / 10 | |
| 5.1.21 | 9 / 10 | |
| 5.1.20 | 9 / 10 | |
| 5.1.18 | 9 / 10 | |
| 5.1.17 | 9 / 10 | |
| 5.1.16 | 9 / 10 | |
| 5.1.14 | 9 / 10 | |
| 5.1.13 | 9 / 10 | |
| 5.1.11 | 9 / 10 | |
| 5.1.10 | 9 / 10 | |
| 5.1.9 | 9 / 10 | |
| 5.1.7 | 9 / 10 | |
| 5.1.2 | 9 / 10 | |
| 5.1.1 | 9 / 10 | |
| 5.1.0 | 9 / 10 | |
| 5.0.7 | 9 / 10 | |
| 5.0.6 | 9 / 10 | |
| 5.0.5 | 9 / 10 | |
| 5.0.4 | 9 / 10 | |
| 5.0.3 | 9 / 10 | |
| 5.0.2 | 9 / 10 | |
| 5.0.1 | 9 / 10 | |
| 5.0.0 | 9 / 10 |
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.