Skip to content

CHANGELOG.md

Latest commit

 

History

History
44 lines (40 loc) · 2.14 KB

CHANGELOG.md

File metadata and controls

44 lines (40 loc) · 2.14 KB
Raw

Changelog

All notable changes to IntelCLI are documented in this file. This project adheres to Semantic Versioning.

[1.0.0] - 2026-07-09

Added

  • Initial public release of IntelCLI.
  • intelcli domain — WHOIS, DNS (A/AAAA/MX/NS/TXT/CNAME/SOA), SSL/TLS certificate inspection, HTTP security-header grading, and lightweight technology detection.
  • intelcli ip — reverse DNS and IP geolocation (via ip-api.com by default, or ipinfo.io when an API token is configured), with private-range detection.
  • intelcli email — syntax validation and MX/DNS deliverability checks, with basic disposable-domain flagging.
  • intelcli username — concurrent presence checks across a dozen public platforms (GitHub, GitLab, Reddit, Instagram, Medium, dev.to, PyPI, Docker Hub, Keybase, Steam, Hacker News, X/Twitter).
  • intelcli company — public company lookup via Clearbit Autocomplete, with optional OpenCorporates integration.
  • intelcli report — auto-detects target type (domain/IP/email/username) and dispatches to the appropriate investigation.
  • intelcli history — local SQLite-backed investigation history with search, limit, and clear support.
  • intelcli config — TOML-based configuration for optional API keys and preferences, with secret redaction and restrictive file permissions.
  • JSON, CSV, and HTML export for every command via --export.
  • Structured logging (rotating file handler + optional verbose console output).
  • Full Rich-powered terminal UI: tables, spinners, colored status messages.
  • Comprehensive test suite: 172 tests, 93%+ coverage, unit + integration.
  • Full documentation set: README, installation guide, usage guide, architecture doc, contributing guide.

Security

  • No hardcoded secrets anywhere in the codebase; all API keys are optional and user-supplied via intelcli config set.
  • Config file is written with 0600 permissions on POSIX systems.
  • All data sources are lawful and publicly documented (standard WHOIS protocol, public DNS, a site's own public HTTPS endpoint, and free/public APIs) — no scraping in violation of terms of service, no unauthorized access.