API Key in the open?
Open
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 555
- Forks
- 140
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 3
Description
Hello! It looks like you have a couple spots where an actual API key for something has been exposed.
I submitted a PR awhile ago to correct this:
https://github.com/nasa/api-docs/pull/171/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's referenced pull request, nasa/api-docs#171, to identify the exposed API-key locations and the proposed scope. Done means the exposed credentials are corrected as addressed by that pull request and the changes are verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100