DevHunt Overview and Ethics

A bounded view of the scan, report, and narrative workflow, with explicit interpretation limits.

What the fixed source does

DevHunt reads GitHub activity that is token-visible for a requested login, stores per-user records locally, derives project-defined descriptive summaries, and can prepare or request an AI-written narrative from the resulting profile. The authenticated GraphQL queries do not limit results to public visibility, so a sufficiently privileged token can expose private or internal-visible repository and pull-request data.

Three-stage workflow

The source exposes three commands: scan, report, and narrate. scan collects inputs, report derives a local profile and charts, and narrate turns that profile into prompts or sends prompt material to a configured provider.

Ethics and interpretation

Availability to the supplied token does not make activity data context-free. Repository history can be incomplete, shared, automated, private, or unrelated to employment. The metrics in this revision are descriptive heuristics defined by the project; they are not validated measures of skill, personality, intelligence, employability, or objective ability.

Safer use

Use the output to inspect source-visible patterns and their sample sizes. Keep unknown values unknown, retain the underlying evidence, avoid ranking people, and remove per-user records when their purpose ends.

Continue

Use Quick Start for the source-backed sequence, Metrics for formulas and unknown behavior, and Data Handling before collecting another person's token-visible metadata.