liukaho/logger-azure
The package has a README, MIT declaration, repository tests, and only two runtime dependencies. It lacks a security policy and has no workflow or security-scanning evidence, while its old Azure integration increases maintenance liability.
38%
Total Score
75
100
83
67
Health Score Breakdown
The package has only one release, published over seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, though the repository remains available and unarchived.
There were no commits and no active maintainers during the last three months, consistent with the package's long period without releases. This materially raises abandonment risk.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide little evidence of an active user or contributor community.
Composer is used as the build tool, but no security-scanning tool is present. For a small package this is a modest transparency and maintenance gap.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is less serious than the package's lack of maintenance activity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 liukaho |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 monolog/monolog Version ^1.24 | — | — |
microsoft/azure-storage-queue Version ^1.1 | — | — |
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 7 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.