JanusGraph / JanusGraph/janusgraph
Add vulnerability check to CI
Open
Nobody has claimed this yet.
kind/enhancement
kind/security
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
While it's great that users report security vulnerabilities as issues it seems like something we should add as an automated check to travis.
Not sure if it should be run with the normal CI or separately on a daily or weekly job.
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 inspecting the repository's Travis CI configuration and current dependency or vulnerability-checking workflow. Decide whether the check belongs in normal CI or a scheduled job, then define completion as an automated vulnerability check running in the chosen CI context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100