frontend-tooling-trust-gate
Review trust before frontend tooling adoption.
SKILL.mdskills/frontend-tooling-trust-gate/SKILL.md
GitHubFrontend Tooling Trust Gate
Use this skill before installing or recommending a repo, package, MCP, plugin, template, or script.
Trust Classes
preferred: official or clearly reputable.acceptable: useful, maintained, and reasonably transparent.inspect manually: promising but insufficiently verified.avoid: suspicious, stale, unsafe, or low-quality.unknown risk: not enough evidence.
Inspection Checklist
- Prefer official sources, verified orgs, and vendor-maintained repos.
- Inspect README specificity, license, SECURITY.md, recent commits, releases, issues, and package registry links.
- Inspect
package.json, scripts, dependencies, and install instructions. - Use
npm view <package> repository license version time maintainerswhen npm metadata matters. - Look for preinstall/postinstall scripts, broad permissions, telemetry, token requests, cookie access, or curl-to-shell commands.
- Prefer project-local installs for frontend tools and libraries.
- Avoid global installs unless the tool is an agent-wide CLI and the user explicitly approves it.
- Never expose API keys, browser cookies, SSH keys, tokens, or private files to unknown tools.
Decision Output
Return:
- source and type
- trust class
- evidence
- red flags
- install stance:
install,project-local only,do not install, orneeds user auth - safer official alternative if rejected
Scope and evidence
Apply to frontend tooling adoption only. Reuse recent verified adoption decisions if no relevant version, source, permission or requirement changed. Stale maintenance is a factor, not proof of malice. Existing authorization covers routine approved installs; spending and external commitments keep their actual boundaries.