The MIT license and matching source repository provide useful transparency. Its install-time scripts and broad runtime dependency set increase maintenance and deployment risk for an already stagnant project.
35%
Total Score
0
50
75
67
The latest release was published over eight years ago, with no releases in the last 12 months. Eight releases clustered within roughly two days show an old initial burst but no continuing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in January 2018. This is strong evidence that maintenance has stopped.
The package declares 14 runtime dependencies and no development dependencies, creating a relatively broad runtime supply chain for a small demonstration application. This is a maintenance and compatibility burden, though it is not severe on its own.
post-install-cmd and post-update-cmd scripts run during Composer operations, increasing installation-time behavior and review requirements. No provided signal shows that these scripts are unnecessary or narrowly scoped.
The linked repository has no security policy and no security scanning tools. For a package that runs maintenance tasks as root, this leaves an important transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
plinker/lxc Version >=v0.1 | — | — |
plinker/core Version >=v0.1 | — | — |
plinker/cron Version >=v0.1 | — | — |
plinker/peer Version dev-master | — | — |
natxet/cssmin Version ^3.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.