@holoscript/framework
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/ai/index.js | AI (source-diff): Bundled dist output, sample shows benign adapter-registry code, no dropper behavior. | ai | |
| source-diff | net-exec-file:dist/index.js | AI (source-diff): Bundled tsup output with standard dynamic-require shim, not a loader payload. | ai | |
| provenance | missing-githead | AI (provenance): Provenance direction unchanged; large monorepo restructure explains build-env change. | ai | |
| 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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.1.5 | 3 / 3 | |
| 6.1.4 | 3 / 3 | |
| 6.1.3 | 3 / 3 | |
| 6.1.2 | 3 / 3 | |
| 6.1.1 | 3 / 3 | |
| 6.1.0 | 3 / 3 | |
| 6.0.4 | 1 / 3 | |
| 6.0.3 | 1 / 3 |
v6.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brianonbased.
v6.1.4
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brianonbased.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.