Caveat verdict

chrome-extension-wxt

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Developer guide for building cross-browser extensions with the WXT framework; credential_access capability is broad but the content only covers standard browser extension development patterns with no exfiltration behavior.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

30
security
40
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (2)

Pattern match critical

<script> tag in markdown — potential code injection

SKILL.md · code · <script

Pattern match high

Dynamic import() — loads module at runtime

references/best-practices.md · code · import('

Permissions & capabilities

No declared permissions — minimal attack surface.

network_incredential_accesspackage_install

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API