@draht/coding-agent
Coding agent CLI with read, bash, edit, write tools and session management
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:steganography-image-eval | AI (semgrep): Flags WAD binary file read for a Doom engine example; no steganography attack pattern present. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 localhost OAuth callback URI — not exfiltration or C2. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used to load a pre-built Doom JS module in an example extension; not a dynamic code injection risk. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes base64 image data and writes to disk in an image-gen example; no payload hiding. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Declared in config files only; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2026.5.12 | 21 / 8 | |
| 2026.4.26 | 20 / 8 | |
| 2026.4.25 | 20 / 8 | |
| 2026.4.23 | 20 / 8 | |
| 2026.4.5 | 21 / 8 |
v2026.5.12
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: execute008.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.26
2 findingsData read from image file then executed — steganography attack pattern 56 | 57 | // Read WAD file > 58 | const wadData = readFileSync(this.wadPath); 59 | const wadArray = Array.from(new Uint8Array(wadData)); 60 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.