Caveat verdict

mapbox-token-security

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

Security best-practices guidance skill for Mapbox token management; purely advisory content about scopes, URL restrictions, and rotation strategies with no operational 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.

0
security
50
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (4)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · Token = 'pk.YOUR_MAPBOX_TOKEN_HERE

Pattern match critical

<script> tag in markdown — potential code injection

AGENTS.md · code · <script>

Pattern match high

HTTP request to bare IP address — common in malicious payloads

SKILL.md · code · http://127.0.0.1

Pattern match medium

Accesses sensitive environment variables

AGENTS.md · code · process.env.NEXT_PUBLIC_MAPBOX_TOKEN

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_access

Is this flag fair?

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