This is my package smart-seeder
62%
Total Score
caution
Usable with caveats: a single-release project has been inactive for three months and uses unpinned CI actions.
One registry account has publish access. The linked repository is owned by the same individual, so this is a small maintainer base rather than a registry-only administrative mismatch; it modestly increases continuity risk.
The registry namespace and repository are owned by the same individual user, providing direct ownership alignment. It does not provide organizational continuity if that maintainer stops contributing.
This package has only one release, published about nine months ago, with no subsequent releases. That limited history provides little evidence of sustained maintenance.
There were zero commits and zero active maintainers in the last three months. Combined with only one release, this is concrete evidence that current maintenance has not yet been demonstrated.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a transparency and hygiene gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^11.0||^12.0 | — | — |
illuminate/contracts Version ^11.0||^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.