@xyo-network/crypto
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): Established XYO Network package with clean history; missing gitHead is a minor publish-env change, not a security signal. | ai | |
| dependencies | unvetted-dep:@xyo-network/pqc | AI (dependencies): Same-org sibling package from XYO Network monorepo, pinned to matching version; consistent with package family pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @xyo-network packages at matching semver; consistent with intra-monorepo PQC feature addition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established XYO Network SDK package; sparse README and no keywords are cosmetic, not indicative of spam. | ai | |
| provenance | no-provenance | AI (provenance): Established XYO Network package; provenance attestation not historically used by this package family. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): LGPL-3.0 is the established license for this package across all versions. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped XYO Network crypto package; not impersonating bcrypt. Levenshtein match is coincidental. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 1 / 23 | |
| 7.0.13 | 9 / 17 | |
| 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 | 9 / 29 | |
| 7.0.4 | 9 / 29 | |
| 7.0.3 | 9 / 27 | |
| 7.0.2 | 9 / 27 | |
| 7.0.0 | 9 / 27 | |
| 6.1.1 | 9 / 27 | |
| 6.1.0 | 9 / 27 | |
| 6.0.9 | 9 / 29 | |
| 6.0.8 | 9 / 30 | |
| 6.0.7 | 9 / 29 | |
| 6.0.6 | 9 / 29 | |
| 6.0.5 | 9 / 32 | |
| 6.0.4 | 9 / 33 | |
| 6.0.3 | 9 / 33 | |
| 6.0.2 | 7 / 32 | |
| 6.0.1 | 7 / 32 | |
| 6.0.0 | 7 / 32 | |
| 5.6.3 | 7 / 32 | |
| 5.6.2 | 7 / 32 | |
| 5.5.2 | 7 / 34 | |
| 5.5.1 | 7 / 34 | |
| 5.5.0 | 7 / 54 | |
| 5.4.1 | 7 / 27 | |
| 5.4.0 | 7 / 27 | |
| 5.3.30 | 7 / 29 | |
| 5.3.29 | 7 / 29 | |
| 5.3.27 | 7 / 35 | |
| 5.3.26 | 7 / 36 | |
| 5.3.25 | 7 / 36 | |
| 5.3.24 | 7 / 36 | |
| 5.3.22 | 7 / 39 | |
| 5.3.20 | 7 / 21 | |
| 5.3.17 | 7 / 20 | |
| 5.3.16 | 7 / 20 | |
| 5.3.15 | 7 / 8 | |
| 5.3.13 | 7 / 8 | |
| 5.3.12 | 7 / 8 | |
| 5.3.11 | 7 / 8 | |
| 5.3.10 | 7 / 8 | |
| 5.3.8 | 7 / 8 | |
| 5.3.7 | 7 / 8 | |
| 5.3.6 | 7 / 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.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.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.29
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.27
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.24
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.20
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonesmac) than the most recent previously approved version (xyo) on 2026-03-30, but jonesmac is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.