Security
Dependency Security Investigator
Dependency Security Investigator
Start with Public repo or dependency inventory. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkEvidence reports
FactoriesStart with your sources
IdleIllustrative runMissing authHigh severity
- Request
- GET /api/invoices/inv_1042
- Response
- 200 OK
Evidence for the pull request200 OK
GET /api/invoices/inv_1042
- Confirmed findings
- 0
- Draft pull requests
- 0
Draft pull requestfix/invoice-session-checkmain
Require a session on GET /api/invoices/[id]
Related solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Dependency Security Investigator
Pick an example, connect your tools, and review the first run.
Set up the Dependency Security Investigator agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Investigate whether new vulnerability reports affect the application's actual dependency use, test bounded updates, and maintain applicability evidence and unresolved questions.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `dependency-security-investigator` is listed, instantiate it with `--path.slug dependency-security-investigator` and start the run; otherwise create a project from this template at /new?template=dependency-security-investigator&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.