NodeSecure / NodeSecure/scanner
Add complete options to controls and securize egress
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- TypeScript
- Stars
- 40
- Forks
- 23
- Avg merge
- 23h 23m
- Merged PRs (30d)
- 2
Description
Right now a lot of workspaces exit to internet:
- Fetching metadata to NPM (or any third-party registry)
- Expired DNS
- ... Etc
The idea is to introduce new configuration (probably also available in RC ?) to manage egress. Some features cannot be disabled but we can maybe have tight controls of what is exiting + disabling optional external requests.
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
No files, tests, or entry points are named. Start by tracing the scanner's external requests, including NPM or other registry metadata fetches and DNS-related behavior, then identify the configuration surface and whether RC exposes it. Done should mean optional egress can be disabled and remaining outbound requests can be explicitly controlled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100