@xyo-network/bios-model
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; missing gitHead is a CI/publish environment change, not a security indicator for this org. | ai | |
| provenance | no-provenance | AI (provenance): XYO Network packages consistently lack Sigstore provenance; not a security risk for this well-established publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Model/type-only package in a monorepo; empty main and minimal README are expected for this package type. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 9.3.1 | 1 / 8 | |
| 9.3.0 | 1 / 10 | |
| 9.2.0 | 1 / 10 | |
| 9.1.1 | 1 / 10 | |
| 9.1.0 | 1 / 10 | |
| 9.0.6 | 1 / 24 | |
| 9.0.5 | 1 / 26 | |
| 9.0.2 | 1 / 27 | |
| 9.0.1 | 1 / 13 | |
| 9.0.0 | 1 / 11 | |
| 8.0.3 | 1 / 11 | |
| 8.0.2 | 1 / 11 | |
| 8.0.1 | 1 / 11 | |
| 8.0.0 | 1 / 16 | |
| 7.4.2 | 1 / 16 | |
| 7.4.1 | 1 / 16 | |
| 7.4.0 | 1 / 16 | |
| 7.3.1 | 1 / 16 | |
| 7.3.0 | 1 / 19 | |
| 7.2.1 | 2 / 3 | |
| 7.2.0 | 2 / 3 | |
| 7.1.0 | 2 / 3 | |
| 7.0.1 | 2 / 3 | |
| 7.0.0 | 2 / 3 |
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
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 (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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
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 (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 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 (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 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 (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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
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 (atrouw) than the most recent previously approved version (jonesmac) on 2026-06-30, 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.0
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 (atrouw) than the most recent previously approved version (jonesmac) on 2026-06-25, 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.