@xyo-network/modules
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): High-volume monorepo publisher with strong approval history; occasional gitHead gaps are not indicative of supply chain compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large monorepo SDK package; sparse README and no keywords are expected for this namespace. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual (joelbcarter) to org account (xyo) with 872 approved packages; consistent with org consolidation. | ai | |
| dependencies | unvetted-dep:@xyo-network/module | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/diviner | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/witness | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/sentinel | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/archivist | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/manifest-wrapper | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/payloadset-plugin | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/boundwitness-loader | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/address-payload-plugin | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/api-location-diviner | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/node | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai | |
| dependencies | unvetted-dep:@xyo-network/bridge | AI (dependencies): Internal monorepo dep from established XYO publisher; version-pinned to same release. | ai |
Versions (showing 51 of 94)
| Version | Deps | Published |
|---|---|---|
| 6.0.4 | 12 / 144 | |
| 6.0.3 | 12 / 145 | |
| 6.0.2 | 12 / 145 | |
| 6.0.1 | 12 / 147 | |
| 6.0.0 | 12 / 164 | |
| 5.6.4 | 12 / 164 | |
| 5.6.3 | 12 / 164 | |
| 5.6.2 | 12 / 166 | |
| 5.6.1 | 12 / 166 | |
| 5.6.0 | 12 / 166 | |
| 5.5.6 | 12 / 167 | |
| 5.5.5 | 12 / 167 | |
| 5.5.3 | 12 / 173 | |
| 5.3.30 | 7 / 175 | |
| 5.3.27 | 7 / 174 | |
| 5.3.26 | 7 / 175 | |
| 5.3.25 | 7 / 175 | |
| 5.3.24 | 7 / 175 | |
| 5.3.22 | 7 / 181 | |
| 5.3.20 | 7 / 163 | |
| 5.3.19 | 7 / 163 | |
| 5.3.17 | 7 / 162 | |
| 5.3.16 | 7 / 162 | |
| 5.3.15 | 7 / 23 | |
| 5.3.14 | 7 / 23 | |
| 5.3.13 | 7 / 23 | |
| 5.3.12 | 7 / 23 | |
| 5.3.11 | 7 / 23 | |
| 5.3.10 | 7 / 23 | |
| 5.3.9 | 7 / 23 | |
| 5.3.8 | 7 / 23 | |
| 5.3.7 | 7 / 23 | |
| 5.3.6 | 7 / 22 | |
| 5.3.5 | 7 / 22 | |
| 5.3.4 | 7 / 22 | |
| 5.3.3 | 7 / 22 | |
| 5.3.2 | 7 / 22 | |
| 5.3.1 | 7 / 22 | |
| 5.3.0 | 7 / 22 | |
| 5.2.27 | 7 / 22 | |
| 5.2.25 | 7 / 22 | |
| 5.2.24 | 7 / 22 | |
| 5.2.23 | 7 / 22 | |
| 5.2.22 | 7 / 22 | |
| 5.2.20 | 7 / 22 | |
| 5.2.19 | 7 / 22 | |
| 5.2.18 | 7 / 23 | |
| 5.2.17 | 7 / 23 | |
| 5.2.16 | 7 / 23 | |
| 5.2.15 | 7 / 23 | |
| 5.2.14 | 7 / 23 |
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
v5.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
v5.6.0
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
v5.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.27
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.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
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.20
2 findingsThis version was published by a different npm account than previous versions on 2026-03-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.19
2 findingsThis version was published by a different npm account than previous versions on 2026-03-30. This could indicate a legitimate maintainer transition or an account compromise.
Package 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.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.24
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.23
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.22
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.20
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package 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.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.