Mapbox Public tokens wrongly identified as Secret tokens in Secret Scanning #198585
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Secret scanning
Discussion Details
Github Secret Scanning currently identifies public mapbox tokens as secret tokens. As per the documentation, all tokens starting with
pkare public tokens, but these are flagged by secret scanning.https://docs.mapbox.com/help/dive-deeper/access-tokens/
I would argue that public tokens do not need to be flagged by secret scanning, as these are meant to be published, and shipped with e.g. frontend apps.
Beta Was this translation helpful? Give feedback.
All reactions