Informational scan, not a security audit. How this is computed.
API keys, passwords or tokens committed into the repo.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
Packages you depend on that have known security holes (CVEs).
CVE-2021-22569 protobuf-java: potential DoS in the parsing procedure for binary dataCVE-2022-3509 protobuf-java: Textformat parsing issue leads to DoSCVE-2022-3510 protobuf-java: Message-Type Extensions parsing issue leads to DoSCVE-2024-7254 protobuf: StackOverflow vulnerability in Protocol BuffersCVE-2022-3171 protobuf-java: timeout in parser leads to DoSCVE-2021-22569 protobuf-java: potential DoS in the parsing procedure for binary dataCVE-2022-3509 protobuf-java: Textformat parsing issue leads to DoSCVE-2022-3510 protobuf-java: Message-Type Extensions parsing issue leads to DoSCVE-2024-7254 protobuf: StackOverflow vulnerability in Protocol BuffersCVE-2022-3171 protobuf-java: timeout in parser leads to DoSYour dependencies cross-checked against the OSV vulnerability database.
GHSA-4gg5-vx3j-xwc7 Protobuf Java vulnerable to Uncontrolled Resource ConsumptionGHSA-735f-pc8j-v9w8 protobuf-java has potential Denial of Service issueGHSA-g5ww-5jh7-63cx Protobuf Java vulnerable to Uncontrolled Resource ConsumptionGHSA-h4h5-3hr4-j3g2 protobuf-java has a potential Denial of Service issueGHSA-wrvw-hg22-4m67 A potential Denial of Service issue in protobuf-javaCode that can be exploited: injection, hardcoded credentials and similar.
Nothing found by this check. ✓
Packages that look intentionally malicious: typosquats, sneaky install scripts.
Nothing found by this check. ✓
A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.
Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.