microsoft / microsoft/OSSGadget
Consider moving crypto library detections to Application Inspector
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- C#
- Stars
- 371
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
We added rules looking for specific common crypto libraries, but we already have a few in Application Inspector. Maybe we should just move them all there, since we're referencing those rules anyway.
Contributor guide
No contributing guide indexed for this repository
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 comparing OSSGadget’s existing crypto-library detection rules with Application Inspector’s cryptography/external_libraries.json. Identify which rules overlap and determine the complete migration scope; done means the duplicated detections have a clear home in Application Inspector and OSSGadget references the intended rules consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- security, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100