Laravel validation rule that checks if a string is offensive.
68%
Total Score
caution
Usable with caveats: all recent repository commits come from one contributor, leaving maintenance capacity concentrated.
All two recent commits came from one contributor, so maintenance and release continuity depend entirely on a single active person.
The repository had two commits in the last three months, showing some ongoing maintenance but a modest pace for a package with recent compatibility work.
The repository has no security policy. For a small validation rule this is a transparency gap rather than a severe risk, but it leaves vulnerability-reporting expectations unclear.
The workflow was fully analyzed, uses read-only permissions, and has no untrusted triggers or injection findings. However, both action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^5.5 || ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
jord-jd/is_offensive Version ^5.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.