The package includes a clear README, release notes, tests in the repository, and an MIT license. Its small dependency footprint and organization-backed repository help, but there is no security policy or security scanning.
38%
Total Score
50
100
71
75
Only two releases were published, both in February 2016, with no release in more than 10 years. This is strong evidence of abandonment for a library dependency.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release hiatus and leaving current maintenance unverified.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was in February 2016 and does not offset the inactive release history.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented; this is a secondary concern for an otherwise inactive project.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
slick/common Version ^1.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.