@xyo-network/core-payload-plugins
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): Known maintainer rotation (jonesmac→xyo); no other risk signals; stable for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removed but atrouw is the same team; org-level maintainer rotation for XYO Network. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw confirmed as known maintainer via email match on prior approved versions. | ai | |
| provenance | publisher-changed-known-maintainer | AI (provenance): atrouw is a known maintainer matched by email; manual publish pattern stable for this org. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): LGPL-3.0-only is the consistent license for this package; not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Established XYO Network package; provenance not historically present, low risk given org track record. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is the explicitly documented consolidation target; package is a re-export stub by design. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentionally minimal stub/deprecation shim; sparse README and no keywords are expected for this pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 849 approved packages; dormancy likely reflects project cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@xyo-network/query-payload-plugin | AI (dependencies): Same-org sibling package at matching version; stable pattern across all xyo-network releases. | ai | |
| dependencies | unvetted-dep:@xyo-network/id-payload-plugin | AI (dependencies): Same-org sibling package at matching version; stable pattern across all xyo-network releases. | ai | |
| dependencies | unvetted-dep:@xyo-network/domain-payload-plugin | AI (dependencies): Same-org sibling package at matching version; stable pattern across all xyo-network releases. | ai | |
| dependencies | unvetted-dep:@xyo-network/config-payload-plugin | AI (dependencies): Same-org sibling package at matching version; stable pattern across all xyo-network releases. | ai | |
| dependencies | unvetted-dep:@xyo-network/value-payload-plugin | AI (dependencies): Same-org sibling package at matching version; stable pattern across all xyo-network releases. | ai |
Versions (showing 100 of 116)
| Version | Deps | Published |
|---|---|---|
| 7.0.14 | 8 / 17 | |
| 7.0.13 | 8 / 18 | |
| 7.0.12 | 1 / 6 | |
| 7.0.11 | 1 / 6 | |
| 7.0.10 | 1 / 6 | |
| 7.0.9 | 1 / 6 | |
| 7.0.8 | 1 / 6 | |
| 7.0.7 | 1 / 6 | |
| 7.0.6 | 1 / 6 | |
| 7.0.5 | 8 / 27 | |
| 7.0.4 | 8 / 27 | |
| 7.0.3 | 8 / 25 | |
| 7.0.2 | 8 / 25 | |
| 7.0.0 | 8 / 25 | |
| 6.1.1 | 8 / 25 | |
| 6.1.0 | 8 / 25 | |
| 6.0.9 | 8 / 27 | |
| 6.0.8 | 8 / 28 | |
| 6.0.7 | 8 / 28 | |
| 6.0.6 | 8 / 28 | |
| 6.0.5 | 8 / 29 | |
| 6.0.4 | 8 / 30 | |
| 6.0.3 | 8 / 30 | |
| 6.0.2 | 8 / 30 | |
| 6.0.1 | 8 / 30 | |
| 6.0.0 | 8 / 30 | |
| 5.6.3 | 8 / 30 | |
| 5.6.2 | 8 / 30 | |
| 5.5.2 | 8 / 33 | |
| 5.5.1 | 8 / 33 | |
| 5.5.0 | 8 / 60 | |
| 5.4.1 | 9 / 29 | |
| 5.4.0 | 9 / 29 | |
| 5.3.30 | 9 / 31 | |
| 5.3.29 | 9 / 31 | |
| 5.3.27 | 9 / 30 | |
| 5.3.26 | 9 / 32 | |
| 5.3.25 | 9 / 32 | |
| 5.3.24 | 9 / 32 | |
| 5.3.22 | 9 / 35 | |
| 5.3.20 | 9 / 16 | |
| 5.3.19 | 9 / 16 | |
| 5.3.17 | 9 / 15 | |
| 5.3.16 | 9 / 15 | |
| 5.3.15 | 9 / 5 | |
| 5.3.14 | 9 / 5 | |
| 5.3.13 | 9 / 5 | |
| 5.3.12 | 9 / 5 | |
| 5.3.11 | 9 / 5 | |
| 5.3.10 | 9 / 5 | |
| 5.3.9 | 9 / 5 | |
| 5.3.8 | 9 / 5 | |
| 5.3.7 | 9 / 5 | |
| 5.3.6 | 9 / 4 | |
| 5.3.5 | 9 / 4 | |
| 5.3.4 | 9 / 4 | |
| 5.3.3 | 9 / 3 | |
| 5.3.2 | 9 / 3 | |
| 5.3.1 | 9 / 3 | |
| 5.3.0 | 9 / 3 | |
| 5.2.27 | 9 / 3 | |
| 5.2.25 | 9 / 3 | |
| 5.2.24 | 9 / 3 | |
| 5.2.23 | 9 / 3 | |
| 5.2.22 | 9 / 3 | |
| 5.2.20 | 9 / 3 | |
| 5.2.19 | 9 / 3 | |
| 5.2.18 | 9 / 3 | |
| 5.2.17 | 9 / 3 | |
| 5.2.16 | 9 / 3 | |
| 5.2.15 | 9 / 3 | |
| 5.2.14 | 9 / 3 | |
| 5.2.13 | 9 / 3 | |
| 5.2.12 | 9 / 3 | |
| 5.2.11 | 9 / 3 | |
| 5.2.10 | 9 / 3 | |
| 5.2.9 | 9 / 3 | |
| 5.2.8 | 9 / 3 | |
| 5.2.7 | 9 / 3 | |
| 5.2.6 | 9 / 3 | |
| 5.2.5 | 9 / 3 | |
| 5.2.2 | 9 / 3 | |
| 5.2.1 | 9 / 3 | |
| 5.2.0 | 9 / 3 | |
| 5.1.24 | 9 / 3 | |
| 5.1.23 | 9 / 3 | |
| 5.1.22 | 9 / 3 | |
| 5.1.21 | 9 / 3 | |
| 5.1.20 | 9 / 3 | |
| 5.1.19 | 9 / 3 | |
| 5.1.18 | 9 / 3 | |
| 5.1.17 | 9 / 3 | |
| 5.1.16 | 9 / 3 | |
| 5.1.15 | 9 / 3 | |
| 5.1.14 | 9 / 3 | |
| 5.1.13 | 9 / 3 | |
| 5.1.11 | 9 / 3 | |
| 5.1.10 | 9 / 3 | |
| 5.1.9 | 9 / 3 | |
| 5.1.8 | 9 / 3 |
v7.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.12
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
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: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
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: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
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: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-05, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.1
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.4.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.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.29
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.27
3 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.
This version was published by a different npm account (xyo) than the most recent previously approved version (jonesmac) on 2026-04-04, but xyo 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.
v5.3.26
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.24
3 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.
This version was published by a different npm account (xyo) than the most recent previously approved version (jonesmac) on 2026-04-02, but xyo 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.
v5.3.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (jonesmac) on 2026-04-02, but xyo 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.
v5.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.19
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonesmac) than the most recent previously approved version (xyo) on 2026-03-30, but jonesmac 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.
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.9
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (joelbcarter) on 2026-01-20, but xyo 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.
v5.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonesmac) than the most recent previously approved version (joelbcarter) on 2026-01-16, but jonesmac 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.
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.15
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (joelbcarter) on 2025-12-01, but xyo 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.
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (joelbcarter) on 2025-11-21, but xyo 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.
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.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.24
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (xyo) than the most recent previously approved version (joelbcarter) on 2025-11-18, but xyo 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.
v5.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.