@casual-simulation/aux-vm-node
A set of utilities required to security run an AUX in Node.js.
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 present; gitHead absence is a CI config change, not a supply-chain concern. | ai | |
| dependencies | unvetted-dep:@casual-simulation/crypto | AI (dependencies): Same org scope; internal dependency of the @casual-simulation ecosystem. | ai | |
| dependencies | unvetted-dep:@casual-simulation/crypto-node | AI (dependencies): Same org scope; internal dependency of the @casual-simulation ecosystem. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@casual-simulation/crypto-node | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): es-toolkit is a declared dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@casual-simulation/crypto | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep false positive for this monorepo package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 9 / 0 | |
| 4.2.3 | 9 / 0 | |
| 4.2.0 | 9 / 0 | |
| 4.1.3 | 9 / 0 | |
| 4.0.1 | 9 / 0 | |
| 4.0.0 | 9 / 0 | |
| 3.10.4 | 9 / 0 | |
| 3.10.3 | 9 / 0 | |
| 3.10.2 | 9 / 0 | |
| 3.8.1 | 9 / 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.3
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.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.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.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.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.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.3
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.