← Home

@xyo-network/boundwitness-builder

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): Likely reflects CI/CD pipeline change when switching to org publisher; no malicious indicators. ai
bogus-package bogus-package AI (bogus-package): Established monorepo package; sparse README and no keywords are cosmetic issues, not risk signals. ai
provenance publisher-changed AI (provenance): Transition to org account 'xyo' with 424 approved packages; consistent with legitimate maintainer consolidation. ai
provenance no-provenance AI (provenance): Large established monorepo; provenance absence is consistent across all versions of this package family. ai

Versions (showing 51 of 110)

View all versions
Version Deps Published
7.0.15 1 / 23
7.0.14 7 / 24
7.0.13 7 / 25
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 7 / 25
7.0.4 7 / 25
7.0.3 7 / 23
7.0.2 7 / 23
7.0.0 7 / 23
6.1.1 7 / 23
6.1.0 7 / 23
6.0.9 7 / 25
6.0.8 7 / 26
6.0.7 7 / 27
6.0.6 7 / 27
6.0.5 6 / 28
6.0.4 6 / 29
6.0.3 6 / 29
6.0.2 6 / 29
6.0.1 6 / 29
6.0.0 6 / 29
5.6.2 6 / 29
5.6.1 6 / 29
5.5.2 6 / 31
5.5.1 6 / 31
5.5.0 3 / 59
5.4.1 4 / 25
5.4.0 4 / 25
5.3.30 4 / 28
5.3.29 4 / 28
5.3.27 7 / 25
5.3.26 7 / 27
5.3.25 7 / 27
5.3.24 7 / 27
5.3.22 7 / 30
5.3.20 7 / 9
5.3.17 7 / 9
5.3.16 7 / 9
5.3.15 7 / 10
5.3.13 7 / 10
5.3.12 7 / 10
5.3.11 7 / 10
5.3.10 7 / 10
5.3.8 7 / 10
5.3.7 7 / 10

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.