anousss007/blatui
A clear README, changelog, release notes, and MIT licensing improve transparency. The project is actively releasing, but one person carries all recent commits and the workflows use unpinned actions with broad release permissions.
78%
Total Score
75
100
94
75
Health Score Breakdown
Only one registry account has publish access. That is a modest continuity concern because the project backing is an individual user rather than an organization.
All 114 recent commits came from one contributor, creating a meaningful continuity risk despite the high commit volume.
Composer build tooling is present, but no security scanning tool was detected. That is a transparency and maintenance gap, not evidence of a security verdict by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
Both workflows were analyzed successfully, with no untrusted checkouts or script injection findings. However, all 23 action references are unpinned, the release workflow grants top-level write permissions, and CI installs packages outside a lockfile, creating workflow hygiene concerns.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 anousss007 |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/console Version ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/support Version ^11.0 || ^12.0 || ^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 days ago
- Created
- 3 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.