engyahmed7/laravel-plaid
The package has a clear README, tests, and an MIT declaration. However, its install-time scripts, absent security scanning, and stale release activity add maintenance and operational risk.
43%
Total Score
50
75
50
Health Score Breakdown
The repository name does not match the package name and its README does not mention the package. This makes the source relationship and provenance difficult to verify.
Four install and update lifecycle scripts run during Composer operations: post-autoload-dump, post-create-project-cmd, post-root-package-install, and post-update-cmd. These may be normal for a Laravel application but increase install-time behavior that consumers must understand.
This package has made only one release, about 14 months ago, with no releases in the last 12 months. That leaves little evidence of sustained maintenance.
The repository had zero commits and zero active maintainers in the last three months. Combined with a single release, this is meaningful evidence of weak current maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance gap for a package handling financial integrations.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/ui Version ^4.6 | — | — |
laravel/tinker Version ^2.10.1 | — | — |
laravel/framework Version ^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.