@holoscript/framework
1
Versions
—
License
No
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
holoscriptagentframeworkmulti-agentknowledgemcp
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP appears only in a test file asserting that OllamaAdapter accepts a custom local baseUrl — not a production network call. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to parse an x402 payment header — standard protocol handling, not obfuscation. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env-spread in build script passes process.env to a child process with an override — common build pattern, not exfiltration. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 6.0.4 | 1 / 3 |
v6.0.4
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.