The repository has no security policy or security scanning, leaving limited evidence of an ongoing maintenance process. A clear README, MIT licensing, and no install-time scripts reduce adoption friction.
60%
Total Score
50
70
75
This package has only one release, published over three years ago, with no releases in the last 12 months. That is meaningful evidence of limited maintenance, although the package may be intentionally small and stable.
The repository recorded no commits and no active maintainers in the last three months, consistent with the lack of follow-up releases. The repository is not archived, which provides some compensating evidence but does not show active maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and assurance gap rather than evidence that the package is unsafe.
No security policy is present in the repository. For a package that handles application errors and sends them to Slack, this reduces transparency about how security issues are reported and managed.
Version 0.1.0 is not marked as a prerelease, but it remains below a stable major version and has no subsequent releases to demonstrate maturity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
maknz/slack Version ^1.7 | — | — |
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.