An implementation of java.util.logging.LogManager
70%
Total Score
caution
Usable with caveats: no commits were recorded in the last three months despite a recent release.
No commits or active maintainers were recorded in the last three months. The recent release and repository push partly offset this, but the short-term activity gap remains a maintenance concern.
All five analyzed action references are unpinned, which weakens workflow reproducibility and update integrity. The audit found no dangerous triggers, untrusted checkouts, script injection, or high-confidence findings.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-10061 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. jboss-logmanager is vulnerable to Uncontrolled Recursion in versions 3.0.3.Final - 3.1.2.Final. | 3.0.3.Final - 3.1.2.Final | Medium |
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
org.jboss.logging:jboss-logging Version 3.6.2.Final | — | — |
org.jboss.modules:jboss-modules Version 2.3.0 | — | — |
io.smallrye.common:smallrye-common-constraint Version * | — | — |
io.smallrye.common:smallrye-common-cpu Version * | — | — |
io.smallrye.common:smallrye-common-expression Version * | — | — |
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.