guanhui07/collections
The MIT license and four runtime dependencies make the package straightforward to inspect and integrate. However, its unusually bulk release history, zero recent commits, missing security policy, and unpinned workflow reference leave maintenance and provenance uncertain.
44%
Total Score
50
100
80
75
Health Score Breakdown
The package has 418 releases but all were published within seconds on 1 November 2024, followed by no releases in the last 12 months. This unusual bulk-release pattern and prolonged silence reduce confidence in normal release maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, despite the package being assessed as a current stable release. That is a meaningful abandonment and maintenance risk.
The linked repository has no security policy, leaving no documented path for reporting vulnerabilities or explaining security handling. This is a transparency gap for a package intended as a dependency.
The only workflow uses a pull_request_target trigger without untrusted checkout or script-injection findings, so the trigger itself is not dangerous. Its single action reference is unpinned, which creates a modest workflow supply-chain hygiene risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Taylor Otwell |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/contracts Version ^11.0 | — | — |
illuminate/macroable Version ^11.0 | — | — |
illuminate/conditionable Version ^11.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 6 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.