SC_Email_Body_with_Known_Phishing_URL takes a long time to populate.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
This signature runs on an automation that adds phishing URLs and keeps the rule in Vetting status. We took a look at this before with Danny and found that the revision history had become bloated from the automated changes and imposed a limit to the number of visible revisions. This rule continues to sit at "Loading ..." until eventually producing an nginx error and appearing in released status after a while.
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the loading behavior for SC_Email_Body_with_Known_Phishing_URL and inspect how automated phishing-URL changes expand revision history. Check the path from the rule's Vetting status through the visible-revision limit to the nginx error. Done means the rule loads reliably and reaches the intended released status without the prolonged delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100