LibChecker/LibChecker

[FR] 和 checksec 联动

Open

#1887 opened on Dec 20, 2025

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Kotlin (6,861 stars) (422 forks)batch import
enhancementhelp wanted

Description

Checklist / 检查清单

  • No one has submitted a similar or identical feature request before. / 之前没有人提交过类似或相同的功能请求。
  • This suggestion does not depart from the original intention of LibChecker. / 这个建议不会背离 LibChecker 的初衷。

Enhancement propose / 改进目的

checksec 可检测 so 的一些安全情况.

Solution / 解决方案

No response

Additional info / 额外信息

No response

Contributor guide

Tech stack
kotlin
Domain
mobilesecurity
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
KotlinAndroidREST API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Explore the checksec API referenced in the issue (https://github.com/slimm609/checksec) to understand its endpoints and data formats. Review LibChecker's existing codebase, particularly how it currently handles native libraries (so files) and displays security related information. Consider discussing in the issue comments how to best integrate checksec, whether through direct HTTP calls or by embedding the tool, and what UI changes would be needed to display the security results.