chrisjohnleah/bigchange-api-laravel
It has a clear README, tests, an MIT license, and no install-time scripts. Unpinned workflow actions and no security policy add modest maintenance and build-hygiene concerns.
68%
Total Score
75
83
50
Health Score Breakdown
The package is only 39 days old and has two releases, so its long-term maturity is not established. The two releases and stable v1.0.1 provide some evidence of an intentional initial release process.
One contributor made 100% of the 15 commits in the last 3 months. Because the repository is user-owned rather than organization-owned, there is no shown organizational handoff path to offset this concentration.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a modest transparency gap for an SDK handling API credentials.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings, but both of its two action references are unpinned. Unpinned actions weaken build reproducibility and supply-chain hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/cache Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
chrisjohnleah/bigchange-api Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 month 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.