← Home

@xyo-network/payload

100
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

atrouwjoelbcarterrphansen91jordantrouwjonesmac

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Likely a CI/publish environment change accompanying the org account transition; no other malware indicators present. ai
provenance publisher-changed AI (provenance): Publisher changed to org account 'xyo' with 439 approved packages — consistent with org consolidation, not compromise. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by publish under established org account with clean track record; no malicious indicators. ai
provenance no-provenance AI (provenance): Large established XYO Network monorepo; provenance absence is consistent across all versions. ai

Versions (showing 100 of 109)

Version Deps Published
7.0.14 5 / 17
7.0.13 5 / 18
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 5 / 26
7.0.4 5 / 26
7.0.3 5 / 24
7.0.2 5 / 24
7.0.0 5 / 24
6.1.1 5 / 24
6.1.0 5 / 24
6.0.9 5 / 26
6.0.8 5 / 27
6.0.7 5 / 27
6.0.6 5 / 27
6.0.5 5 / 27
6.0.4 5 / 28
6.0.3 5 / 28
6.0.2 5 / 28
6.0.1 5 / 28
6.0.0 5 / 28
5.6.3 5 / 28
5.6.2 5 / 28
5.5.2 5 / 31
5.5.1 5 / 31
5.5.0 5 / 56
5.4.1 5 / 23
5.4.0 5 / 23
5.3.30 5 / 26
5.3.29 5 / 26
5.3.27 5 / 24
5.3.26 5 / 26
5.3.25 5 / 26
5.3.24 5 / 26
5.3.22 5 / 24
5.3.20 5 / 14
5.3.17 5 / 13
5.3.16 5 / 13
5.3.15 5 / 5
5.3.13 5 / 5
5.3.12 5 / 5
5.3.11 5 / 5
5.3.10 5 / 5
5.3.8 5 / 5
5.3.7 5 / 5
5.3.6 5 / 4
5.3.5 5 / 4
5.3.4 5 / 4
5.3.3 5 / 3
5.3.2 5 / 3
5.3.1 5 / 3
5.3.0 5 / 3
5.2.27 5 / 3
5.2.25 5 / 3
5.2.24 5 / 3
5.2.22 5 / 3
5.2.20 5 / 3
5.2.19 5 / 3
5.2.18 5 / 3
5.2.17 5 / 3
5.2.16 5 / 3
5.2.14 5 / 3
5.2.13 5 / 3
5.2.12 5 / 3
5.2.11 5 / 3
5.2.10 5 / 3
5.2.9 5 / 3
5.2.8 5 / 3
5.2.7 5 / 3
5.2.6 5 / 3
5.2.5 5 / 3
5.2.1 5 / 3
5.2.0 5 / 3
5.1.24 5 / 3
5.1.23 5 / 3
5.1.22 5 / 3
5.1.21 5 / 3
5.1.20 5 / 3
5.1.19 5 / 3
5.1.18 5 / 3
5.1.17 5 / 3
5.1.16 5 / 3
5.1.15 5 / 3
5.1.14 5 / 3
5.1.13 5 / 3
5.1.10 5 / 3
5.1.9 5 / 3
5.1.8 5 / 3
5.1.7 5 / 3
5.1.6 5 / 3
5.1.5 5 / 3
5.1.4 5 / 3
5.1.3 5 / 3
5.1.2 5 / 3
5.1.1 5 / 3
Showing 100 of 109 Next page →

v7.0.14

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.13

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.