There is no security policy or repository scanning, and the project has only three files. The MIT declaration and simple dependency profile reduce adoption friction.
42%
Total Score
0
100
75
67
The package has made only one release, published in August 2020, with no releases in the last 12 months. That is strong evidence of abandonment risk for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the lack of releases since August 2020. The inactive development history materially lowers confidence in ongoing maintenance.
The published artifact and repository each contain only README.md, composer.json, and src/slackApi.php. The small footprint may fit this narrowly scoped package, but it provides little evidence of broader project maturity.
Composer is used for the build, but no security scanning tools are configured. That reduces evidence of routine dependency and code-security maintenance.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it is not independently severe enough to make the package unfit.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.