always-open/report-engine
The repository includes tests, release notes, security tooling, and a security policy. Workflow images are unpinned, adding avoidable build-supply-chain exposure.
58%
Total Score
63
100
89
100
Health Score Breakdown
There were zero commits and zero active maintainers in the last three months. Combined with the last push being about 18 months ago, this is a material abandonment risk.
The package has 43 releases since August 2022, but none in the last 12 months and the latest release was about 18 months ago. This points to meaningful maintenance risk despite its established history.
There were no new issues, closed issues, pull requests, or merged pull requests in the last month, consistent with the observed maintenance slowdown.
The repository has six stars and two forks, indicating limited adoption. Popularity is supporting evidence rather than a health verdict, so this is only a minor concern.
Both workflows were analyzed with no untrusted triggers or script-injection findings, but all five action references are unpinned and a high-confidence audit found an unpinned container image. This creates avoidable workflow supply-chain risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 AlwaysOpen |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 brick/money Version ^0.10.0 | — | — |
always-open/sidekick Version ^5.1 | — | — |
illuminate/contracts Version ^11.0|^12.0 | — | — |
spatie/laravel-package-tools Version ^1.19.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 5 years 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.