@xyo-network/protocol
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): Package is a re-export stub under active refactor; environment change explains missing gitHead, not a supply-chain indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @xyo-network/sdk-protocol, the org's own package being consolidated into; expected for this deprecation stub. | ai | |
| provenance | no-provenance | AI (provenance): Established XYO Network package; lack of provenance is a process gap, not a malice indicator for this org. | ai | |
| dependencies | unvetted-dep:@xyo-network/core | AI (dependencies): Same-org monorepo sibling dependency; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@xyo-network/crypto | AI (dependencies): Same-org monorepo sibling dependency; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@xyo-network/boundwitness | AI (dependencies): Same-org monorepo sibling dependency; version-locked to matching release. | ai |
Versions (showing 51 of 109)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 1 / 23 | |
| 7.0.14 | 4 / 20 | |
| 7.0.13 | 4 / 21 | |
| 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 | 4 / 57 | |
| 7.0.4 | 4 / 57 | |
| 7.0.3 | 4 / 55 | |
| 7.0.2 | 4 / 55 | |
| 7.0.0 | 4 / 55 | |
| 6.1.1 | 4 / 55 | |
| 6.1.0 | 4 / 55 | |
| 6.0.9 | 4 / 57 | |
| 6.0.8 | 4 / 58 | |
| 6.0.7 | 4 / 56 | |
| 6.0.6 | 4 / 56 | |
| 6.0.5 | 4 / 59 | |
| 6.0.4 | 4 / 60 | |
| 6.0.3 | 4 / 60 | |
| 6.0.2 | 4 / 57 | |
| 6.0.1 | 4 / 57 | |
| 6.0.0 | 4 / 57 | |
| 5.6.3 | 4 / 57 | |
| 5.6.2 | 4 / 57 | |
| 5.5.2 | 4 / 59 | |
| 5.5.1 | 4 / 59 | |
| 5.5.0 | 4 / 79 | |
| 5.4.1 | 4 / 64 | |
| 5.3.30 | 4 / 67 | |
| 5.3.29 | 4 / 67 | |
| 5.3.27 | 4 / 60 | |
| 5.3.26 | 4 / 61 | |
| 5.3.25 | 4 / 61 | |
| 5.3.24 | 4 / 61 | |
| 5.3.22 | 4 / 64 | |
| 5.3.20 | 4 / 49 | |
| 5.3.17 | 4 / 48 | |
| 5.3.16 | 4 / 48 | |
| 5.3.15 | 4 / 5 | |
| 5.3.13 | 4 / 5 | |
| 5.3.12 | 4 / 5 | |
| 5.3.11 | 4 / 5 | |
| 5.3.10 | 4 / 5 | |
| 5.3.8 | 4 / 5 | |
| 5.3.7 | 4 / 5 | |
| 5.3.6 | 4 / 4 |
v7.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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 (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.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
2 findings[Accepted risk] Package 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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
3 findings[Accepted risk] Package 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.
This version was published by a different npm account (xyo) than the most recent previously approved version (joelbcarter) on 2026-04-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.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.29
2 findings[Accepted risk] Package 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.3.27
3 findings[Accepted risk] Package 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.
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 findings[Accepted risk] Package 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.3.25
2 findings[Accepted risk] Package 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.3.24
2 findings[Accepted risk] Package 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.3.22
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 (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
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 (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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.16
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 (xyo) than the most recent previously approved version (joelbcarter) on 2026-03-11, 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.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.