@xyo-network/schema-name-validator
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): Established package in a large monorepo ecosystem; sparse README and no keywords are consistent across the XYO suite. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; lack of provenance is consistent across all XYO Network packages. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 1 / 23 | |
| 7.0.14 | 0 / 5 | |
| 7.0.13 | 0 / 6 | |
| 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 | 0 / 6 | |
| 7.0.4 | 0 / 6 | |
| 7.0.3 | 0 / 4 | |
| 7.0.2 | 0 / 4 | |
| 7.0.0 | 0 / 4 | |
| 6.1.1 | 0 / 4 | |
| 6.1.0 | 0 / 4 | |
| 6.0.9 | 0 / 4 | |
| 6.0.8 | 0 / 4 | |
| 6.0.6 | 0 / 4 | |
| 6.0.5 | 0 / 4 | |
| 6.0.4 | 0 / 4 | |
| 6.0.3 | 0 / 4 | |
| 6.0.2 | 0 / 4 | |
| 6.0.1 | 0 / 4 | |
| 6.0.0 | 0 / 4 | |
| 5.6.3 | 0 / 4 | |
| 5.5.2 | 0 / 5 | |
| 5.5.1 | 0 / 5 | |
| 5.5.0 | 0 / 28 | |
| 5.4.1 | 0 / 3 | |
| 5.4.0 | 1 / 7 | |
| 5.3.24 | 1 / 12 | |
| 5.3.22 | 1 / 14 | |
| 5.3.17 | 1 / 3 | |
| 5.3.16 | 1 / 3 | |
| 5.3.15 | 1 / 3 | |
| 5.3.13 | 1 / 3 | |
| 5.3.12 | 1 / 3 | |
| 5.3.11 | 1 / 3 | |
| 5.3.10 | 1 / 3 | |
| 5.3.8 | 1 / 3 | |
| 5.3.7 | 1 / 3 | |
| 5.3.6 | 1 / 3 | |
| 5.3.5 | 1 / 3 | |
| 5.3.4 | 1 / 3 | |
| 5.3.2 | 1 / 3 | |
| 5.3.1 | 1 / 3 | |
| 5.3.0 | 1 / 3 | |
| 5.2.27 | 1 / 3 | |
| 5.2.25 | 1 / 3 |
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.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.