afom/deploy-notifier
Tests, a clear README, and a matching repository improve transparency. The organization-backed project is not archived, but its code and releases have been untouched for over nine years.
38%
Total Score
75
100
88
75
Health Score Breakdown
The package has had no releases in more than nine years: all six releases occurred on December 21, 2016, with none in the last 12 months. This is strong evidence of abandonment risk.
The repository has no new issues, closed issues, pull requests, or merged pull requests in the last month. Combined with the last push being over nine years ago, this supports a caution about inactive maintenance.
Composer is used for builds, but no security scanning tools are present. This is a minor transparency and hygiene gap rather than evidence that the package is unsafe to depend on.
The repository has no security policy. For a small, inactive package this weakens vulnerability-reporting transparency, though it is less significant than the prolonged lack of releases.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 AFOM Development team |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/console Version ^5.0,<5.5 | — | — |
illuminate/support Version ^5.0,<5.5 | — | — |
gorkalaucirica/hipchat-v2-api-client Version ^1.5 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.