@highflame/overwatch
Standalone security daemon for IDE-agnostic AI agent security
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used only for binary path resolution (where/which equivalent); not executing user-supplied or remote input. | ai | |
| phantom-deps | phantom-dep:ejs | AI (phantom-deps): esbuild-bundled package; static analysis misses bundled imports. | ai | |
| phantom-deps | phantom-dep:open | AI (phantom-deps): esbuild-bundled package; static analysis misses bundled imports. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): esbuild-bundled package; static analysis misses bundled imports. | ai | |
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): esbuild-bundled package; static analysis misses bundled imports. | ai | |
| phantom-deps | phantom-dep:@highflame/policy | AI (phantom-deps): Same-org dep; likely bundled or loaded at runtime via platform-specific optional dep. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.0.10 | 3 / 6 | |
| 2.0.9 | 3 / 6 | |
| 2.0.0 | 2 / 6 | |
| 1.0.15 | 2 / 6 | |
| 1.0.14 | 2 / 6 | |
| 1.0.13 | 6 / 7 | |
| 1.0.12 | 6 / 7 | |
| 1.0.11 | 6 / 7 | |
| 1.0.10 | 6 / 7 | |
| 1.0.9 | 6 / 7 | |
| 1.0.8 | 6 / 7 | |
| 1.0.7 | 6 / 7 | |
| 1.0.6 | 6 / 7 | |
| 1.0.4 | 6 / 7 |
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
2 findingsThis version was published by a different npm account than previous versions on 2026-07-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.