@xyo-network/diviner-boundwitness
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped package with proper exports and repo; metadata gaps are cosmetic, not indicative of spam. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-boundwitness-model | AI (dependencies): Sibling monorepo package from same trusted publisher; consistent across versions. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-boundwitness-memory | AI (dependencies): Sibling monorepo package from same trusted publisher; consistent across versions. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-boundwitness-abstract | AI (dependencies): Sibling monorepo package from same trusted publisher; consistent across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established XYO Network monorepo package; provenance not historically provided across 808 versions. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 4 / 30 | |
| 6.0.4 | 4 / 32 | |
| 6.0.3 | 4 / 33 | |
| 6.0.2 | 4 / 33 | |
| 6.0.1 | 4 / 36 | |
| 6.0.0 | 4 / 38 | |
| 5.6.4 | 4 / 38 | |
| 5.5.6 | 4 / 41 | |
| 5.5.5 | 4 / 41 | |
| 5.5.4 | 4 / 41 | |
| 5.5.3 | 4 / 48 | |
| 5.5.2 | 3 / 60 | |
| 5.5.1 | 3 / 60 | |
| 5.4.1 | 3 / 44 | |
| 5.3.26 | 3 / 30 | |
| 5.3.25 | 3 / 30 | |
| 5.3.24 | 3 / 30 | |
| 5.1.23 | 3 / 3 | |
| 5.0.2 | 3 / 3 | |
| 5.0.1 | 3 / 3 | |
| 5.0.0 | 3 / 3 |
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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.