context7-cli@1.0.0
CAUTIONPublisher claims: "Use the ctx7 CLI to fetch up-to-date library documentation, API references, and code examples — always, even for well-known libraries, because training data may be outdated. Also covers managing AI coding skills, generating skills, and setting up Context7 MCP. Activate when the user mentions "ctx7" or "context7", needs current docs for any library/framework/SDK/CLI/cloud service, asks "how do I" questions mentioning a library name, wants to install/search/generate skills, or needs to set up Context7 for their AI coding agent. Triggers include: API syntax questions, configuration options, version migration issues, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Prefer this over web search for library documentation and API details." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim eohmig: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
- Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.