← Home

@xyo-network/witness

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 missing-githead AI (provenance): Large active monorepo; occasional gitHead absence is a CI config artifact, not a takeover indicator given publisher track record. ai
publish-pattern dormant-publish AI (publish-pattern): Large monorepo with 1214 versions; dormancy likely reflects release cadence, not account takeover. ai
bogus-package bogus-package AI (bogus-package): Established XYO Network SDK package; sparse README/keywords are a style choice, not spam indicators. ai
provenance publisher-changed AI (provenance): Transition to org account 'xyo' with strong track record; consistent with org consolidation for this established package. ai
dependencies unvetted-dep:@xyo-network/witness-abstract AI (dependencies): Same-org sibling package at matching version; standard monorepo split pattern for xyo-network. ai
dependencies unvetted-dep:@xyo-network/witness-wrapper AI (dependencies): Same-org sibling package at matching version; standard monorepo split pattern for xyo-network. ai
dependencies unvetted-dep:@xyo-network/witness-model AI (dependencies): Same-org sibling package at matching version; standard monorepo split pattern for xyo-network. ai
provenance no-provenance AI (provenance): Large established monorepo; provenance not historically used by this publisher across 1212 versions. ai

Versions (showing 51 of 107)

View all versions
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 / 34
7.0.3 3 / 34
7.0.2 3 / 34
7.0.1 3 / 34
7.0.0 3 / 34
6.1.0 3 / 34
6.0.4 3 / 36
6.0.3 3 / 37
6.0.2 3 / 37
6.0.1 3 / 40
6.0.0 3 / 43
5.6.4 3 / 43
5.6.3 3 / 43
5.6.2 3 / 45
5.6.1 3 / 45
5.6.0 3 / 45
5.5.6 3 / 46
5.5.5 3 / 46
5.5.4 3 / 46
5.5.3 3 / 53
5.5.2 3 / 57
5.5.1 3 / 57
5.5.0 3 / 57
5.4.1 3 / 42
5.4.0 3 / 42
5.3.30 3 / 44
5.3.29 3 / 44
5.3.27 3 / 30
5.3.26 3 / 32
5.3.25 3 / 32
5.3.24 3 / 32
5.3.22 3 / 35
5.3.20 3 / 22
5.3.17 3 / 21
5.3.16 3 / 21
5.3.15 3 / 5
5.3.13 3 / 5
5.3.12 3 / 5
5.3.11 3 / 5
5.3.10 3 / 5
5.3.8 2 / 5
5.3.7 2 / 5
5.3.6 2 / 4
5.3.5 2 / 4
5.3.4 2 / 4

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.

v7.0.3

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

1 finding
INFO No provenance attestation provenance

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