The MIT license and matching source repository provide clear provenance. Its extremely brief README and install-time scripts leave limited guidance and add avoidable maintenance friction.
40%
Total Score
50
64
50
The package has had only one release, published in October 2017, with no releases in the last 12 months. That is strong evidence of abandonment for a library dependency.
The repository had zero commits and zero active maintainers in the last three months. Combined with the old release history, this indicates a substantial abandonment risk.
The package declares eight install- and update-time Composer lifecycle scripts. Their presence increases installation complexity and warrants caution, although this signal alone does not show that the scripts are unsafe.
The package includes a README and GitHub release notes for this version, but the README is only 18 characters long. Missing tests and changelog files are normal for a published artifact and are not treated as gaps.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. This is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
siriussupreme/sirius-support Version ^1.0 | — | — |
siriussupreme/sirius-filesystem Version ^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.