@casual-simulation/aux-vm-client
A set of utilities required to securely run an AUX as a client.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is a metadata gap, not a security risk for this well-established package. | ai | |
| dependencies | unvetted-dep:@casual-simulation/crypto | AI (dependencies): Same-org monorepo sibling; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@casual-simulation/timesync | AI (dependencies): Same-org monorepo sibling; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@casual-simulation/websocket | AI (dependencies): Same-org monorepo sibling; consistent pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@casual-simulation/crypto | AI (phantom-deps): Same-org sibling dep in a monorepo; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 13 / 0 | |
| 4.2.3 | 13 / 0 | |
| 4.2.2 | 13 / 0 | |
| 4.1.5 | 13 / 0 | |
| 4.1.3 | 13 / 0 | |
| 4.0.5 | 13 / 0 | |
| 4.0.1 | 13 / 0 | |
| 3.10.4 | 13 / 0 | |
| 3.10.2 | 13 / 0 | |
| 3.8.1 | 13 / 0 |
v4.2.4
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.