← Home

@highflame/overwatch

npm

Standalone security daemon for IDE-agnostic AI agent security

12
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

akhiljavelinakashjavelinsharathrajasekar

Keywords

securityvalidationjavelinguardrailsdaemonipcai-securitymcpide-securitycursorclaude-code

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 12 of 12)

Version Deps Published
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.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.9

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.

v1.0.8

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.

v1.0.7

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.

v1.0.6

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.

v1.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.