The tech-fingerprint repository extracts technology‑level fingerprints from raw observations (HTML, HTTP headers, TLS certificates, etc.) and produces structured Technology entities.
Planning – repository only contains a placeholder README.
A dedicated fingerprinting service allows the rest of the pipeline to work with high‑level technology identifiers (e.g., web server, CMS, framework) without each component re‑implementing detection logic.
- Library – imported by
entity-extractorandchange-detector. - Exposes a Go package
github.com/FLATLINEDSTAR/tech-fingerprintwith a function:func Fingerprint(obs OnionObservation) ([]Technology, error)
- Header‑based detection (Server, X‑Powered‑By).
- TLS‑certificate analysis (issuer, key length).
- HTML meta‑tag and script‑src heuristics.
- Simple rule‑engine driven by a YAML fingerprint database.
# Go (primary)
go get github.com/FLATLINEDSTAR/tech-fingerprintPackage will be released after MVP is complete.
- Language: Go.
- Follow organization‑wide contribution guidelines.
- Unit tests for each detection rule.
- Integration tests covering real‑world
.onionservices (using mock data).
See the organization‑wide CONTRIBUTING.md in the .github repository.
- Phase 1 – Define
Technologystruct inonion-sdkand populate a basic fingerprint rule set. - Phase 2 – Implement detection logic and CI pipeline for rule updates.
- Phase 3 – Expose Python/TS bindings via the SDK.
tech-fingerprint enriches raw observations, feeding entity-extractor and change-detector, which subsequently provide data to onion-intelligence.
MIT – see LICENSE in the repository root.