sagentic@1.0.5
Production-grade autonomous AI agent platform optimized for Google Cloud Run, Neon pgvector, and Gemini/Cloudflare
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI's default remote path forwards AUTH_SECRET or API_SECRET to a fixed publisher-hosted service, creating a concrete credential disclosure path. Local mode and endpoint overrides exist, but neither guards the default remote path.
Decision evidence
public snapshot- The CLI defaults to a fixed publisher-hosted chat endpoint.
- In remote mode, the CLI selects AUTH_SECRET, API_SECRET, or env.AUTH_SECRET as its bearer token and sends it in the request to that endpoint.
- Remote requests are made for each submitted message unless local mode is explicitly enabled.
- The manifest has no install lifecycle hook; the behavior requires a user to run the CLI and submit a message.
- Users can configure a different endpoint or explicitly select local mode.
Source & flagged code
5 flagged · loading sourcePackage source references dynamic code evaluation.
dist/tools/data-calculator.jsView on unpkg · L18Source appears to send environment or credential material to an external endpoint.
dist/security/auth.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to sagentic@1.0.5.
See all versions of sagentic for other recorded verdicts.
- Avoid installing sagentic@1.0.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.