@xyo-network/bridge-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Large established SDK monorepo; sparse README and no keywords are cosmetic issues, not spam indicators. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 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 / 28 | |
| 5.6.4 | 3 / 28 | |
| 5.5.6 | 3 / 28 | |
| 5.5.5 | 3 / 28 | |
| 5.5.4 | 3 / 28 | |
| 5.5.3 | 3 / 36 | |
| 5.5.2 | 3 / 36 | |
| 5.5.1 | 3 / 36 | |
| 5.5.0 | 3 / 36 | |
| 5.4.1 | 3 / 19 | |
| 5.4.0 | 3 / 19 | |
| 5.2.22 | 4 / 3 | |
| 5.2.20 | 4 / 3 | |
| 5.1.24 | 4 / 3 | |
| 5.1.23 | 4 / 3 | |
| 5.1.22 | 4 / 3 | |
| 5.1.21 | 4 / 3 | |
| 5.1.20 | 4 / 3 | |
| 5.1.18 | 4 / 3 | |
| 5.1.17 | 4 / 3 | |
| 5.1.16 | 4 / 3 | |
| 5.1.14 | 4 / 3 | |
| 5.1.13 | 4 / 3 | |
| 5.1.11 | 4 / 3 | |
| 5.1.10 | 4 / 3 | |
| 5.1.9 | 4 / 3 | |
| 5.1.7 | 4 / 3 | |
| 5.1.2 | 4 / 3 | |
| 5.1.1 | 4 / 3 | |
| 5.1.0 | 4 / 3 | |
| 5.0.7 | 4 / 3 | |
| 5.0.6 | 4 / 3 | |
| 5.0.5 | 4 / 3 | |
| 5.0.4 | 4 / 3 | |
| 5.0.3 | 4 / 3 | |
| 5.0.2 | 4 / 3 | |
| 5.0.1 | 4 / 3 | |
| 5.0.0 | 4 / 3 |
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.