Caveat verdict

next-best-practices

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

Reference skill providing Next.js coding best practices; purely informational with no capabilities, credentials, or external calls.

⚠ 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.

0
security
90
transparency
70
maintenance

Findings (5)

Pattern match critical

<script> tag in markdown — potential code injection

bundling.md · code · <script

Pattern match critical

Possible hardcoded credential

scripts.md · code · apiKey="YOUR_API_KEY

Pattern match high

Dynamic import() — loads module at runtime

bundling.md · code · import('

Pattern match high

Instructs covert action — may act without user awareness

rsc-boundaries.md · code · silently

Pattern match low

Makes HTTP request to external URL

data-patterns.md · code · fetch('https://

Permissions & capabilities

No declared permissions — minimal attack surface.

Is this flag fair?

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