hanzoasashi/laravel-bpjs-bridging
The repository has a matching package, an MIT license, tests, and Dependabot scanning. Its workflows use broad permissions and unpinned actions, while the high-confidence bot-condition warning adds release-process concern.
43%
Total Score
25
79
50
Health Score Breakdown
Only two releases exist, both from July 2023, with no releases in the last 12 months and no subsequent registry activity for about three years. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating little current maintenance capacity.
The package and repository are owned by the same individual account rather than an organization. This does not imply a problem, but it provides less visible backing for a project already showing prolonged inactivity.
No repository security policy is present. This is a transparency and maintenance gap, though it is less significant than the release and commit inactivity.
The assessed release is v0.0.2 and the package has not reached a stable major version. That is a maturity concern, especially alongside the absence of later releases.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Hansen Makangiras |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.7 | — | — |
illuminate/contracts Version ^10.0 | — | — |
nullpunkt/lz-string-php Version ^1.3 | — | — |
spatie/laravel-package-tools Version ^1.14.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 3 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.