The repository has no security policy or automated security scanning, which weakens transparency. MIT licensing, a clear README, and organization backing provide useful adoption support.
60%
Total Score
67
100
88
75
The package has 12 releases since July 2016, but none in the last 12 months and the latest release was about two years ago. This is a meaningful maintenance concern for a dependency, despite the established release history.
The repository recorded zero commits and zero active maintainers in the last three months. Together with the stale release history, this raises the risk that fixes and compatibility updates may not arrive promptly.
There were no new or closed issues or pull requests in the last month. This is consistent with a quiet project and modestly reinforces the maintenance concern, though it does not by itself show abandonment.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. That weakens vulnerability-reporting transparency, with no provided compensating security process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tigron/skeleton-core Version >=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.