The ISC license and package README support straightforward adoption. No security policy or scanning adds maintenance and disclosure uncertainty.
42%
Total Score
25
100
79
50
The package has had no release in more than six years, despite six releases in its first few months; 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 reducing confidence in ongoing maintenance.
One individual has registry publish access. That is not inherently unsafe, but without recent activity or organization backing it leaves the project with a thin apparent maintainer base.
The artifact and repository each contain only README.md and composer.json. The README identifies this as a subtree split, so the small tree may be intentional, but it provides little transparency into implementation or testing.
Composer is used for build and dependency management, which is appropriate, but no security scanning tooling was detected. This is a hygiene gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phased/state Version self.version | — | — |
phased/routing Version self.version | — | — |
spatie/laravel-server-side-rendering Version ^1.4.1 | — | — |
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.