@xyo-network/diviner-schema-stats
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 | publisher-changed | AI (provenance): jonesmac is an established publisher with 3731 approved packages; transition appears legitimate for this org. | ai | |
| provenance | missing-githead | AI (provenance): Large XYO monorepo with consistent publish patterns; likely CI environment change, not a takeover signal. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 3522 approved packages; dormancy reflects project cadence, not account compromise. | ai | |
| provenance | no-provenance | AI (provenance): Large established XYO Network monorepo; provenance not used across their package ecosystem. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-schema-stats-memory | AI (dependencies): Sibling package from same XYO monorepo at matching version; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner-schema-stats-abstract | AI (dependencies): Sibling package from same XYO monorepo at matching version; stable pattern across all releases. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 1 / 9 | |
| 7.2.0 | 1 / 11 | |
| 7.1.1 | 1 / 11 | |
| 7.1.0 | 1 / 11 | |
| 7.0.11 | 1 / 24 | |
| 7.0.10 | 1 / 25 | |
| 7.0.9 | 3 / 25 | |
| 7.0.8 | 3 / 27 | |
| 7.0.7 | 3 / 25 | |
| 7.0.6 | 3 / 25 | |
| 7.0.5 | 3 / 25 | |
| 7.0.4 | 3 / 25 | |
| 7.0.3 | 3 / 25 | |
| 7.0.2 | 3 / 25 | |
| 7.0.1 | 3 / 25 | |
| 7.0.0 | 3 / 25 | |
| 6.1.0 | 3 / 25 | |
| 6.0.4 | 3 / 27 | |
| 6.0.3 | 3 / 28 | |
| 6.0.2 | 3 / 28 | |
| 6.0.1 | 3 / 31 | |
| 6.0.0 | 3 / 33 | |
| 5.6.4 | 3 / 33 | |
| 5.6.3 | 3 / 33 | |
| 5.6.2 | 3 / 33 | |
| 5.6.1 | 3 / 33 | |
| 5.6.0 | 3 / 33 | |
| 5.5.6 | 3 / 33 | |
| 5.5.5 | 3 / 33 | |
| 5.5.4 | 3 / 33 | |
| 5.5.3 | 3 / 40 | |
| 5.5.2 | 3 / 49 | |
| 5.5.1 | 3 / 49 | |
| 5.5.0 | 3 / 49 | |
| 5.4.1 | 3 / 32 | |
| 5.4.0 | 3 / 32 | |
| 5.3.30 | 3 / 34 | |
| 5.3.29 | 3 / 34 | |
| 5.3.27 | 3 / 18 | |
| 5.3.26 | 3 / 22 | |
| 5.3.25 | 3 / 22 | |
| 5.3.24 | 3 / 22 | |
| 5.3.22 | 3 / 25 | |
| 5.3.20 | 3 / 12 | |
| 5.3.19 | 3 / 12 | |
| 5.3.17 | 3 / 11 | |
| 5.3.16 | 3 / 11 | |
| 5.3.15 | 3 / 5 | |
| 5.3.14 | 3 / 5 | |
| 5.3.13 | 3 / 5 | |
| 5.3.12 | 3 / 5 |
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.