Evidence policy
Honeystax combines automated discovery with editorial curation. A listing is a research lead, not an endorsement or security guarantee.
Project facts come from linked GitHub repositories and project sites. Hacker News supplies discussion signal. Honeystax upvotes are a separate community-interest signal.
Repository stars, commit dates, archive state, issue counts, and community-health fields are timestamped when checked. Each tool page shows its source and latest check date.
Curated boards favor a clear developer use case, a verifiable source, recent maintenance, meaningful adoption signal, and enough documentation to test the tool.
Risk is a Honeystax analysis of archive state, commit age, open issues, community health, security policy, contributing guide, and code of conduct. It is not a vulnerability scan.
Featured status, source traction, freshness, and practical test cost guide editorial order. Paid placement does not determine source metrics or risk labels.
Source owners can use the Submit path to provide a corrected canonical URL or updated facts. Honeystax rechecks the authoritative source before changing measured fields.