@foxxytux/buddy-coding-agent
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): Flagged code reads a Doom WAD file in an examples/extensions directory — legitimate game engine example, not a steganography attack. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in examples/extensions/antigravity-image-gen.ts is standard image data handling, not payload delivery. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:8080/callback is a localhost OAuth redirect URI — standard OAuth PKCE flow in a GitLab Duo extension example. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() used to load a compiled Doom JS/WASM module in an examples/extensions file — legitimate emscripten module loading pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for Windows toast notifications via powershell.exe in an examples/extensions/notify.ts file — benign notification utility. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for this package; no other indicators of supply chain risk. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.1.28 | 22 / 8 | |
| 4.1.26 | 21 / 8 | |
| 4.1.25 | 21 / 8 | |
| 4.1.16 | 21 / 8 | |
| 4.1.15 | 21 / 8 | |
| 4.1.14 | 21 / 8 | |
| 4.1.11 | 21 / 8 | |
| 4.1.10 | 21 / 8 | |
| 4.1.9 | 21 / 8 | |
| 4.1.8 | 21 / 8 | |
| 4.1.7 | 21 / 8 | |
| 4.1.6 | 21 / 8 | |
| 4.1.5 | 21 / 8 | |
| 4.1.4 | 21 / 8 | |
| 4.1.3 | 21 / 8 | |
| 4.1.2 | 21 / 8 | |
| 4.0.4 | 21 / 8 |
v4.1.28
2 findingsData read from image file then executed — steganography attack pattern Source: https://github.com/badlogic/pi-mono/blob/53db12204d7319db9dc284cd0cd4cb3e4d63e43c/examples/extensions/doom-overlay/doom-engine.ts#L58 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.
v4.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.