The source still includes tests, a README, and a matching repository, while licensing is clear. Its small dependency set and organization ownership offer some context, but not enough evidence of active support.
40%
Total Score
50
71
50
The package has had no release in over five years, with five releases total and none in the last 12 months. This is strong evidence of abandonment risk, though the repository is not archived.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository remains available, but there is no recent maintenance evidence.
The package defines a post-root-package-install script, so installation performs additional automated work. This deserves some caution because lifecycle behavior increases installation complexity, but the signal does not show malicious behavior.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is secondary to the maintenance concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
makise-co/auth Version ~2.0.0 | — | — |
makise-co/http Version ~2.0.0 | — | — |
makise-co/framework Version ~2.0.0 | — | — |
middlewares/payload Version ^3.0 | — | — |
makise-co/orm-bundle Version ~2.0.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.