The project has tests, a changelog, clear licensing, and no install-time scripts. It has seen no release activity since December 2015, has minimal adoption, and lacks a security policy; pinning this old release carries abandonment risk.
45%
Total Score
67
75
The package has only two releases, both published on December 30, 2015, with no releases in the last 12 months; this is strong evidence of long-term inactivity.
The repository has zero stars and forks and only one watcher, indicating very limited visible adoption and support capacity.
Composer is used as the build tool, but no security-scanning tools are present; the missing scanning is a modest hygiene concern rather than proof of unsafe code.
The linked repository is not archived, although its last push was on December 30, 2015; the lack of archival status is positive but does not offset the age of the activity.
The repository has no security policy, leaving vulnerability-reporting expectations unclear; this is a minor transparency gap for a dependency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
container-interop/container-interop Version 1.1.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.