lirantal / lirantal/nodejs-runtime-security
Ndoe.js runtime experimental regex engine rule
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
As [recommended](https://x.com/poledesfetes/status/1952660764478648454) by Vladimir:
```
~ node --enable-experimental-regexp-engine-on-excessive-backtracks -e \ "const r=/(a*)*b/; console.time('t'); r.test('a'.repeat(1e6)); console.timeEnd('t')" t: 99.461ms ➜ ~ node -e \ "const r=/(a*)*b/; console.time('t'); r.test('a'.repeat(1e6)); console.timeEnd('t')" ... still running
```
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 only provides a Node.js command using --enable-experimental-regexp-engine-on-excessive-backtracks and a catastrophic-backtracking regex example. Start by determining the intended runtime rule and its scope; the issue does not name files, tests, or a clear completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100