Caveat verdict

mapbox-google-maps-migration

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

Reference documentation and code patterns for migrating from Google Maps to Mapbox GL JS; purely educational content with no executable 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.

20
security
50
transparency
70
maintenance

Permission integrity

Performs file operations but does not declare file-accessing binaries

file_read

Findings (4)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · Token = 'YOUR_MAPBOX_TOKEN

Pattern match critical

<script> tag in markdown — potential code injection

SKILL.md · code · <script

Pattern match medium

Accesses sensitive environment variables

AGENTS.md · code · process.env.NEXT_PUBLIC_MAPBOX_TOKEN

Pattern match low

Makes HTTP request to external URL

AGENTS.md · code · fetch( `https://

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_accessnetwork_infile_read

Is this flag fair?

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