slimm609/checksec

Health v2 · maintenance only

Flags: no_license

Adoption not part of the score

2371 stars · 314 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A Go rewrite of the classic checksec tool that inspects security hardening properties (RELRO, stack canaries, NX, PIE, FORTIFY_SOURCE, CFI) of ELF executables, running processes, and the Linux kernel. It ships as a single static binary with CLI, JSON, XML, and YAML output formats.

Use cases

• check if a binary is compiled with PIE, RELRO, and stack canaries
• audit security hardening of executables in a directory
• verify binary hardening in distroless containers or embedded systems
• check the running kernel's hardening configuration
• scan a running process's security properties by PID
• output binary security checks as JSON for CI pipelines

When to choose

• you need fast, dependency-free binary security checks on Linux
• you want machine-readable output (JSON/XML/YAML) for automation
• you're auditing hardening flags across many binaries or in minimal environments
• you need to check kernel or process hardening from the command line

When to avoid

• you need to analyze Windows PE or macOS Mach-O binaries
• you need full feature parity with the original bash checksec
• you need deep binary analysis beyond hardening flags, such as disassembly or vulnerability discovery

Facets

cli-tool · maturity active

security vulnerability-scanning cli developer-tools security developer-tools cli go binary-analysis elf hardening-checks single-binary penetration-testing command-line linux macos docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="slimm609/checksec")