# Know what a package will run before it is installed (slim)

> Know what a package will run before it is installed: 0 companies fully do it, 0 with a limit, 1 carry the tag. Every listing in Agent package managers with the reason and a source.

- Full: https://www.anchorterminal.com/niches/agent-packages.vet-before-install/index.md (~650 tokens) · this version ~230 tokens · JSON https://www.anchorterminal.com/niches/agent-packages.vet-before-install/index.json · canonical https://www.anchorterminal.com/niches/agent-packages.vet-before-install/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all. Full fit: 0 companies, with a limit: 0, tagged: 1. Weight 13, 5 accounts.

Done when: The tool states what runs at add, sync and launch (scripts, hooks, MCP servers started), lists them for the package before install, asks or refuses before running any, and never reads credentials such as gh or env tokens without saying so. Hooks and MCP servers added by an update are shown as a change.

Data: https://www.anchorterminal.com/api/v1/use-cases/agent-packages.vet-before-install.json
