@holoscript/security-sandbox MIT 3 versions

@holoscript/security-sandbox

npm Repository Homepage

VM-based sandbox for secure HoloScript execution - protects against AI-generated code injection

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

brianonbased

Keywords

holoscriptsecuritysandboxvmai-safetycode-execution

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@holoscript/engine	AI (phantom-deps): Same-org scoped dep in a monorepo; likely re-exported or used indirectly.	ai	2026/05/14

Versions (showing 3 of 3)

Version	Deps	Published
1.2.4	3 / 7	2026-06-08
1.2.2	3 / 7	2026-05-03
1.2.0	2 / 5	2026-03-23

v1.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.