The package includes a clear README, matching source repository, license, and test files in the repository. Its one-person ownership, minimal adoption, and missing security policy leave little resilience.
58%
Total Score
50
80
50
Only two releases exist, with no releases in the last 12 months; the latest was published about 15 months ago. This indicates limited ongoing maintenance for a package first released about 17 months ago.
The repository had no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. The non-archived repository provides some continuity, but not evidence of current maintenance.
The repository has 1 star, 0 forks, and 1 watcher, providing little evidence of broad community use or external review. Low popularity is supporting evidence rather than a standalone failure for a small utility.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less serious than evidence of unsafe release behavior.
The single workflow was fully analyzed with no reported audit findings or untrusted execution paths, but all 3 action references are unpinned. The workflow also lacks a top-level permissions block, which is acceptable on its own but leaves dependency pinning as a hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^3 | — | — |
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.