The single registry publisher fits organization ownership, and the focused runtime dependency set keeps integration simple. Missing security documentation and weak repository-to-package identification reduce transparency.
78%
Total Score
100
100
88
83
100
The repository name does not match this package and its README does not mention the package, so the package-to-source relationship is less transparent despite the broader organization backing.
The project uses Gradle and CMake, but no security-scanning tools were detected. This is a transparency and hygiene gap, not evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for a security-sensitive TLS library.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-550833 bctls-lts8on is vulnerable to Improper Certificate Validation in versions 2.73.0 - 2.73.11. | 2.73.0 - 2.73.11 | High |
AIKIDO-2026-54143 bctls-lts8on is vulnerable to Denial of Service (DoS) in versions 2.73.0 - 2.73.11. | 2.73.0 - 2.73.11 | Medium |
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
org.bouncycastle:bcutil-lts8on Version 2.73.13 | — | — |
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.