@xyo-network/payload-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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): XYO publishes many packages in bulk; missing gitHead appears to be a CI environment change, not a supply-chain indicator given clean publisher history. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to org account 'xyo' with 439 approved packages — consistent with org-level consolidation, not compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with org account migration; no suspicious code changes introduced. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all versions and not a security concern here. | ai |
Versions (showing 51 of 110)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 1 / 23 | |
| 7.0.14 | 2 / 14 | |
| 7.0.13 | 2 / 15 | |
| 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 | 2 / 15 | |
| 7.0.4 | 2 / 15 | |
| 7.0.3 | 2 / 13 | |
| 7.0.2 | 2 / 13 | |
| 7.0.0 | 2 / 13 | |
| 6.1.1 | 2 / 13 | |
| 6.1.0 | 2 / 13 | |
| 6.0.9 | 2 / 16 | |
| 6.0.8 | 2 / 17 | |
| 6.0.7 | 2 / 17 | |
| 6.0.6 | 2 / 17 | |
| 6.0.5 | 2 / 17 | |
| 6.0.4 | 2 / 18 | |
| 6.0.3 | 2 / 18 | |
| 6.0.2 | 2 / 18 | |
| 6.0.1 | 2 / 18 | |
| 6.0.0 | 2 / 18 | |
| 5.6.3 | 2 / 18 | |
| 5.6.2 | 2 / 18 | |
| 5.5.2 | 2 / 20 | |
| 5.5.1 | 2 / 20 | |
| 5.5.0 | 2 / 40 | |
| 5.4.1 | 2 / 13 | |
| 5.4.0 | 2 / 13 | |
| 5.3.30 | 2 / 15 | |
| 5.3.29 | 2 / 15 | |
| 5.3.27 | 2 / 15 | |
| 5.3.26 | 2 / 16 | |
| 5.3.25 | 2 / 16 | |
| 5.3.24 | 2 / 16 | |
| 5.3.22 | 2 / 17 | |
| 5.3.20 | 2 / 6 | |
| 5.3.17 | 2 / 6 | |
| 5.3.16 | 2 / 6 | |
| 5.3.15 | 2 / 7 | |
| 5.3.13 | 2 / 7 | |
| 5.3.12 | 2 / 7 | |
| 5.3.11 | 2 / 7 | |
| 5.3.10 | 2 / 7 | |
| 5.3.8 | 2 / 7 | |
| 5.3.7 | 2 / 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.