LosLog integration for Hermes
58%
Total Score
67
79
75
The package has only two releases, both published nearly ten years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, despite the repository showing recent activity.
All recent repository commits came from one contributor, so maintenance depends on a single active person. Organization backing provides some handoff capacity, but no second active contributor is shown.
The repository recorded one commit by one active maintainer in the last three months. This recent activity partly offsets the old registry release history but is too sparse to establish a strong maintenance cadence.
The repository name matches the package, so it appears to belong to this release, but its README does not mention the package. That weakens repository-to-package transparency slightly.
Composer is used for builds, but no security-scanning tooling is present. The missing scanning is a modest transparency gap rather than evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
los/loslog Version ~1.0 | — | — |
mt-olympus/hermes Version ~0.9 | — | — |
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.