Detect use of unsafe language features
Open
Nobody has claimed this yet.
enhancement
needs discussion
static analysis
- Dominant language
- Go
- Stars
- 912
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
Via static analysis where possible.
e.g.
- JNDI
- Unsafe code in memory safe languages
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
The issue names no files, tests, or entry points. Start by identifying the repository's static-analysis entry point and how package languages are detected, then define which unsafe features to recognize, including JNDI and unsafe code in memory-safe languages. Done means the analysis detects the agreed feature set with tests covering the supported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100