@xyo-network/boundwitness-wrapper
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): Well-established XYO monorepo package; missing gitHead likely reflects a CI pipeline change, not a supply-chain risk. | ai | |
| provenance | publisher-changed | AI (provenance): jonesmac is an established publisher (880 approved) within the XYO org; transition appears legitimate. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party @xyo-network/* packages at matching version pins; not a third-party supply-chain risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established XYO Network SDK package; sparse README/keywords are a consistent pattern across the org, not spam. | ai | |
| provenance | no-provenance | AI (provenance): Long-established XYO Network package; provenance absence is consistent across its many versions. | ai |
Versions (showing 51 of 109)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 1 / 23 | |
| 7.0.14 | 7 / 21 | |
| 7.0.13 | 7 / 22 | |
| 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 | 7 / 22 | |
| 7.0.4 | 7 / 22 | |
| 7.0.3 | 7 / 20 | |
| 7.0.2 | 7 / 20 | |
| 7.0.0 | 7 / 20 | |
| 6.1.1 | 7 / 20 | |
| 6.1.0 | 7 / 20 | |
| 6.0.9 | 7 / 22 | |
| 6.0.7 | 7 / 24 | |
| 6.0.6 | 7 / 24 | |
| 6.0.5 | 7 / 25 | |
| 6.0.4 | 7 / 26 | |
| 6.0.3 | 7 / 26 | |
| 6.0.2 | 6 / 26 | |
| 6.0.1 | 6 / 26 | |
| 6.0.0 | 6 / 26 | |
| 5.6.2 | 6 / 26 | |
| 5.6.1 | 6 / 26 | |
| 5.5.2 | 6 / 28 | |
| 5.5.1 | 6 / 28 | |
| 5.5.0 | 4 / 57 | |
| 5.4.1 | 4 / 24 | |
| 5.4.0 | 4 / 24 | |
| 5.3.30 | 4 / 26 | |
| 5.3.29 | 4 / 26 | |
| 5.3.27 | 6 / 21 | |
| 5.3.26 | 6 / 23 | |
| 5.3.25 | 6 / 23 | |
| 5.3.24 | 6 / 23 | |
| 5.3.22 | 6 / 26 | |
| 5.3.20 | 6 / 7 | |
| 5.3.17 | 6 / 7 | |
| 5.3.16 | 6 / 7 | |
| 5.3.15 | 6 / 8 | |
| 5.3.13 | 6 / 8 | |
| 5.3.12 | 6 / 8 | |
| 5.3.11 | 6 / 8 | |
| 5.3.10 | 6 / 8 | |
| 5.3.8 | 6 / 8 | |
| 5.3.7 | 6 / 8 | |
| 5.3.6 | 6 / 7 |
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
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.