NodeSecure / NodeSecure/scanner
(Scanner) Unified cache layer ?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 40
- Forks
- 23
- Avg merge
- 23h 23m
- Merged PRs (30d)
- 2
Description
Outside of pacote (who manage it's own local cache on the system) we currently have no unified cache layer to share between scans which is a problem when doing the same work again and again between multiple runs
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 locating the scanner's scan orchestration and any existing cache integrations, then review how pacote manages its local cache. Done should be defined as a shared cache that avoids repeating work across separate scans.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100