@xyo-network/diviner-payload-pointer
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 |
|---|---|---|---|---|
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): Stable LGPL-3.0-only license across all versions of this package; not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large established monorepo; sparse README and no keywords are expected for sub-packages. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-payload-pointer-model | AI (dependencies): Same-org monorepo sibling dependency; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-payload-pointer-memory | AI (dependencies): Same-org monorepo sibling dependency; version-locked to matching release. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 5.6.4 | 2 / 51 | |
| 5.5.0 | 2 / 69 | |
| 5.3.25 | 2 / 42 | |
| 5.3.22 | 2 / 45 | |
| 5.3.17 | 2 / 31 | |
| 5.3.16 | 2 / 31 | |
| 5.3.15 | 2 / 3 | |
| 5.3.14 | 2 / 3 | |
| 5.3.13 | 2 / 3 | |
| 5.3.12 | 2 / 3 | |
| 5.3.11 | 2 / 3 | |
| 5.3.10 | 2 / 3 | |
| 5.3.8 | 2 / 3 | |
| 5.3.7 | 2 / 3 | |
| 5.3.6 | 2 / 3 | |
| 5.3.5 | 2 / 3 | |
| 5.3.4 | 2 / 3 | |
| 5.3.3 | 2 / 3 | |
| 5.3.2 | 2 / 3 | |
| 5.3.1 | 2 / 3 | |
| 5.3.0 | 2 / 3 | |
| 5.2.27 | 2 / 3 | |
| 5.2.25 | 2 / 3 | |
| 5.2.19 | 2 / 3 | |
| 5.2.18 | 2 / 3 | |
| 5.2.17 | 2 / 3 | |
| 5.2.16 | 2 / 3 | |
| 5.2.14 | 2 / 3 | |
| 5.2.13 | 2 / 3 | |
| 5.2.12 | 2 / 3 | |
| 5.2.11 | 2 / 3 | |
| 5.2.10 | 2 / 3 | |
| 5.2.9 | 2 / 3 | |
| 5.2.8 | 2 / 3 | |
| 5.2.7 | 2 / 3 | |
| 5.2.6 | 2 / 3 | |
| 5.2.5 | 2 / 3 | |
| 5.2.1 | 2 / 3 | |
| 5.2.0 | 2 / 3 | |
| 5.1.24 | 2 / 3 | |
| 5.1.21 | 2 / 3 | |
| 5.1.20 | 2 / 3 | |
| 5.1.18 | 2 / 3 | |
| 5.1.17 | 2 / 3 | |
| 5.1.16 | 2 / 3 | |
| 5.1.14 | 2 / 3 | |
| 5.1.13 | 2 / 3 | |
| 5.1.10 | 2 / 3 | |
| 5.1.9 | 2 / 3 | |
| 5.1.7 | 2 / 3 | |
| 5.1.2 | 2 / 3 |
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.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.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.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.24
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.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.