mikesamuel / attack-review-testbedLinks
Make it easy to probe the strengths and weaknesses of a hardened Node.js stack
☆19Updated 6 years ago
Alternatives and similar repositories for attack-review-testbed
Users that are interested in attack-review-testbed are comparing it to the libraries listed below
Sorting:
- Security design pattern support for Node.js☆24Updated 6 years ago
- Discussion area for security aspects of ECMAScript☆64Updated 7 years ago
- Security advisories for Node.js and the JavaScript ecosystem.☆41Updated 4 years ago
- A zoo for malicious NPM packages☆20Updated 2 years ago
- Policy management tool for Node.js☆22Updated 2 years ago
- umbrella config to achieve scanjs-like functionality through eslint☆88Updated 3 years ago
- An extensible, heuristic-based vulnerability scanning tool for installed npm packages☆50Updated 3 years ago
- rules for scanjs functionality☆28Updated 3 years ago
- Fast and simple way to check any HTTP Headers☆46Updated last year
- Intentionally Vulnerable Node Applications☆16Updated 5 years ago
- Snyk Node Runtime Agent☆16Updated 3 years ago
- Automatically Preventing Code Injection Attacks on Node.js☆78Updated 3 years ago
- A developer-friendly secrets detection tool for CI and pre-commit hooks based on Yelp's detect-secrets☆51Updated 3 years ago
- ESLint plugin with rules for finding security issues in React projects.☆18Updated 3 years ago
- JavaScript parser and sandbox☆78Updated 8 years ago
- Derive property based testing fast-check into a fuzzer for REST APIs☆39Updated 4 years ago
- A documentation and tracking project with the goal of making package management systems more secure.☆50Updated 4 years ago
- A Modest Content Security Proposal☆40Updated 3 years ago
- "Will I break you" - a tool for testing dependents☆39Updated last week
- Report URI JS☆39Updated 7 years ago
- Content-Security-Policy report aggregator/analyzer☆54Updated 5 years ago
- WebAppSec Content Security Policy☆220Updated last week
- Listo. Use questionnaires and checklists to make it easy to do the right thing, regarding the software you build.☆28Updated 2 years ago
- Create a Content-Security-Policy for a website based on the statically detectable relations☆76Updated last week
- Some thoughts on how Node.js might respond to a changing security environment☆173Updated 6 years ago
- An npm beholder that deceives you☆31Updated 5 months ago
- ESLint plugin to detect and stop Trojan Source attacks☆77Updated 2 years ago
- A Common Weakness Enumeration (CWE) Node.js SDK compliant with MITRE / CAPEC☆32Updated 4 months ago
- ☆39Updated 2 years ago
- TSLint security rules☆69Updated 4 years ago