laramint/laravel-stress
It includes a usable README, tests, and a clear MIT license. The project is only 138 days old, and its single workflow leaves all 8 action references unpinned; no security policy is provided.
76%
Total Score
100
100
94
83
Health Score Breakdown
Composer build tooling is present, but no security-scanning tool is configured; this is a modest transparency gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
The workflow audit completed successfully with no dangerous triggers, untrusted checkouts, or findings, but all 8 of 8 action references are unpinned, weakening build reproducibility and supply-chain control.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0|^8.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.0|^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 18 days ago
- Created
- 5 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.