58%
Total Score
caution
A small, single-maintainer project has had no commits for three months after releasing three versions in one day.
Only one registry publishing account is listed, leaving limited visible publishing capacity. The repository is also owned by an individual, so there is no organizational backing signal to compensate for the thin maintainer base.
The registry namespace and repository owner are the same individual account, confirming ownership alignment but not broader organizational backing.
The package is 235 days old with three releases, all clustered within roughly 3 hours, and no later release activity is shown. This suggests an immature release history with limited evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the clustered initial releases, this is meaningful evidence of weak ongoing maintenance.
The repository has zero stars, forks, and watchers, providing no supporting evidence of community adoption or external review. Popularity is supporting evidence only, so this is a minor concern rather than a decisive risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^3.10 | — | — |
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.