@casual-simulation/aux-vm-browser
A set of utilities required to securely run an AUX in a web browser.
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 cosmetic given CI/CD publish with Sigstore attestation. | ai | |
| dependencies | unvetted-dep:@casual-simulation/crypto | AI (dependencies): Same-org scoped dependency from a long-established monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@casual-simulation/websocket | AI (dependencies): Same-org scoped dependency from a long-established monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@casual-simulation/crypto-browser | AI (dependencies): Same-org scoped dependency from a long-established monorepo; not a third-party risk. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:bowser | AI (phantom-deps): bowser is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@casual-simulation/crypto | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@casual-simulation/crypto-browser | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 17 / 1 | |
| 4.2.3 | 17 / 1 | |
| 4.2.2 | 17 / 1 | |
| 4.2.0 | 17 / 1 | |
| 4.1.4 | 17 / 1 | |
| 4.1.3 | 17 / 1 | |
| 4.1.0 | 17 / 1 | |
| 3.10.5 | 17 / 1 | |
| 3.10.4 | 17 / 1 | |
| 3.10.2 | 17 / 1 | |
| 3.8.1 | 17 / 1 |
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.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.4
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.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.5
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.