@xyo-network/bios
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of a large established SDK monorepo; sparse README and no keywords are expected for internal sub-packages. | ai | |
| typosquat | typosquat.levenshtein:axios | AI (typosquat): Scoped @xyo-network package; Levenshtein match to axios is a false positive with no brand impersonation. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 9.3.1 | 4 / 10 | |
| 9.3.0 | 4 / 12 | |
| 9.2.0 | 4 / 12 | |
| 9.1.1 | 4 / 12 | |
| 9.1.0 | 4 / 12 | |
| 9.0.6 | 2 / 27 | |
| 9.0.5 | 2 / 29 | |
| 9.0.2 | 2 / 30 | |
| 9.0.1 | 2 / 30 | |
| 9.0.0 | 2 / 30 | |
| 8.0.3 | 2 / 30 | |
| 8.0.2 | 2 / 30 | |
| 8.0.1 | 2 / 30 | |
| 8.0.0 | 2 / 51 | |
| 7.4.2 | 2 / 51 | |
| 7.4.1 | 2 / 51 | |
| 7.4.0 | 2 / 51 | |
| 7.3.1 | 2 / 51 | |
| 7.3.0 | 2 / 55 | |
| 7.2.1 | 4 / 4 | |
| 7.2.0 | 4 / 4 | |
| 7.1.0 | 4 / 4 | |
| 7.0.1 | 4 / 4 | |
| 7.0.0 | 4 / 4 |
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-15, but atrouw 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.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
2 findingsPackage 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 (atrouw) on 2026-07-14, 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.
v9.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (jonesmac) on 2026-07-13, but atrouw 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.
v9.0.6
2 findingsPackage 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 (atrouw) on 2026-07-13, 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.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.