The MIT license, substantial README, and matching organization repository improve transparency. No security scanning and minimal adoption signals provide little additional assurance for a long-lived dependency.
40%
Total Score
50
100
75
50
The package has 60 releases but none in the last 12 months; its latest release was in May 2018, about 8 years ago. This strongly increases abandonment risk, despite its substantial historical release count.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the last push in May 2018. The repository is not archived, but there is no observed recent maintenance.
The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these numbers provide no independent sign of active adoption.
Composer is used for the build, but no security scanning tool is configured. That is a hygiene gap that reduces ongoing assurance without proving the package is unsafe.
The repository has no security policy. This limits vulnerability-reporting transparency, though it is less significant than the prolonged lack of maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
plinker/core Version >=0.1 | — | — |
league/climate Version ^3.2 | — | — |
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.