@xyo-network/diviner-payload-pointer-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, 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): High-volume XYO monorepo publisher; likely CI environment change, not a compromise signal. | ai | |
| provenance | publisher-changed | AI (provenance): joelbcarter is an established XYO org publisher with 2565 approved packages; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large monorepo package; sparse README and no keywords are consistent across the XYO Network package family. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance not yet configured but consistent across all versions. | ai |
Versions (showing 51 of 113)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 2 / 13 | |
| 7.2.0 | 2 / 15 | |
| 7.1.1 | 2 / 15 | |
| 7.1.0 | 2 / 15 | |
| 7.0.11 | 2 / 28 | |
| 7.0.10 | 2 / 29 | |
| 7.0.9 | 5 / 35 | |
| 7.0.8 | 5 / 37 | |
| 7.0.7 | 5 / 35 | |
| 7.0.6 | 5 / 35 | |
| 7.0.5 | 5 / 35 | |
| 7.0.4 | 5 / 35 | |
| 7.0.3 | 5 / 35 | |
| 7.0.2 | 5 / 35 | |
| 7.0.1 | 5 / 35 | |
| 7.0.0 | 5 / 35 | |
| 6.1.0 | 5 / 35 | |
| 6.0.4 | 5 / 37 | |
| 6.0.3 | 5 / 38 | |
| 6.0.2 | 5 / 38 | |
| 6.0.1 | 5 / 41 | |
| 6.0.0 | 5 / 46 | |
| 5.6.4 | 5 / 46 | |
| 5.6.3 | 7 / 44 | |
| 5.6.2 | 7 / 46 | |
| 5.6.1 | 7 / 46 | |
| 5.6.0 | 7 / 46 | |
| 5.5.6 | 7 / 47 | |
| 5.5.5 | 7 / 47 | |
| 5.5.3 | 7 / 54 | |
| 5.5.2 | 3 / 67 | |
| 5.5.1 | 3 / 67 | |
| 5.5.0 | 3 / 67 | |
| 5.4.1 | 6 / 48 | |
| 5.3.30 | 6 / 51 | |
| 5.3.29 | 6 / 51 | |
| 5.3.27 | 11 / 39 | |
| 5.3.26 | 11 / 41 | |
| 5.3.25 | 11 / 41 | |
| 5.3.24 | 11 / 41 | |
| 5.3.22 | 11 / 44 | |
| 5.3.20 | 11 / 25 | |
| 5.3.19 | 11 / 25 | |
| 5.3.17 | 11 / 24 | |
| 5.3.16 | 11 / 24 | |
| 5.3.15 | 8 / 25 | |
| 5.3.14 | 8 / 25 | |
| 5.3.13 | 8 / 25 | |
| 5.3.12 | 8 / 25 | |
| 5.3.11 | 8 / 25 | |
| 5.3.10 | 8 / 25 |
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-07-13, but joelbcarter 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.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.