← Home

@xyo-network/key-model

51
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 no-provenance AI (provenance): No provenance is typical for this publisher/package lineage. ai
publish-pattern dormant-publish AI (publish-pattern): Publisher xyo has 849 approved packages; dormancy likely reflects monorepo release cadence, not account takeover. ai
provenance publisher-changed AI (provenance): xyo org account with 448 approved packages; consistent with org-level publisher consolidation across the monorepo. ai
bogus-package bogus-package AI (bogus-package): Small model/type package in a large monorepo; sparse README and empty entry point are expected for this package type. ai

Versions (showing 51 of 102)

View all versions
Version Deps Published
7.0.15 1 / 23
7.0.14 1 / 11
7.0.13 1 / 12
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 1 / 12
7.0.4 1 / 12
7.0.3 1 / 10
7.0.2 1 / 10
7.0.0 1 / 10
6.1.1 1 / 10
6.1.0 1 / 10
6.0.9 1 / 13
6.0.8 1 / 14
6.0.7 1 / 14
6.0.6 1 / 14
6.0.5 1 / 14
6.0.4 1 / 15
6.0.3 1 / 15
6.0.2 1 / 15
6.0.1 1 / 15
6.0.0 1 / 15
5.6.3 1 / 15
5.5.0 1 / 37
5.4.0 1 / 7
5.3.29 1 / 9
5.3.24 1 / 12
5.3.22 1 / 14
5.3.20 1 / 4
5.3.17 1 / 3
5.3.16 1 / 3
5.3.15 1 / 4
5.3.13 1 / 4
5.3.12 1 / 4
5.3.11 1 / 4
5.3.10 1 / 4
5.3.8 1 / 4
5.3.7 1 / 4
5.3.6 1 / 4
5.3.5 1 / 4
5.3.4 1 / 4
5.3.3 1 / 4
5.3.2 1 / 4
5.3.1 1 / 4
5.3.0 1 / 4
5.2.27 1 / 4

v7.0.15

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.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.