NodeSecure / NodeSecure/vulnera
Implement Node.js dependency vuln assessments in Node.js
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 14
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
One of the goal of Vulnera is to re-implement the following Node project that was written in Python: https://github.com/nodejs/nodejs-dependency-vuln-assessments/tree/main
What's the progression:
- NVD database implementation
- GitHub Advisory database
Note that the python script is using GitHub GraphQL API to fetch vulnerability:
github_vulnerabilities_query = gql(
"""
query($package_name:String!) {
securityVulnerabilities(package:$package_name, last:10) {
nodes {
vulnerableVersionRange
advisory {
ghsaId
permalink
withdrawnAt
}
}
}
}
"""
)
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 with the linked nodejs-dependency-vuln-assessments project and its dep_checker/main.py GraphQL query. Compare that behavior with Vulnera’s existing NVD database implementation, then implement the unchecked GitHub Advisory database progression in TypeScript. Done means GitHub Advisory vulnerabilities are fetched using the documented query fields for Node.js dependency assessments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, graphql, node.js, typescript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100