blissjaspis/laravel-midtrans
The documentation, tests, release notes, and recent commits provide useful maintenance evidence. There is no security policy or automated security scanning, and registry publishing remains concentrated in one maintainer.
78%
Total Score
75
100
94
88
Health Score Breakdown
Only one registry account has publish access, which concentrates release authority. The repository's recent activity from two contributors partly offsets that concern, but does not remove it.
The registry namespace and repository owner are the same individual account. This makes ownership clear, though it also means there is no shown organizational backing to compensate for maintainer concentration.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning lowers process maturity without indicating abandonment or an immediate dependency risk.
The repository has no security policy. For a payment-integration package, this is a transparency and incident-reporting gap that is not covered by the otherwise solid documentation.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Bliss Jaspis |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/http Version ^11.0 || ^12.0 || ^13.0 | — | — |
guzzlehttp/guzzle Version ^7.9 | — | — |
illuminate/support Version ^11.0 || ^12.0 || ^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 year 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.