Study the repository before inheriting its assumptions.
ForkSense examines current code, maintenance, known problems, rejected proposals, active forks, contributor work, and executable evidence before Torsionfield adopts, wraps, extracts, forks, or declines external software.
Default branch, releases, recent commits, tests, issues, TODOs, and actual operational use.
Distinguish technical failure, scope mismatch, timing, duplication, security, licensing, and unknown reasons.
Trace ancestry, unique patches, maintenance, tests, adoption, and upstream synchronization burden.
Build or test the leading candidate instead of choosing by stars, prose, or popularity.
One repository, two real candidates.
- Ingest current branches, releases, issues, pull requests, reviews, and recent commits.
- Find one rejected or deferred proposal and one active fork or successor.
- Revise the research route once in response to evidence.
- Produce two competing integration candidates.
- Run a bounded build or code-level test.
- Return a current recommendation with freshness, uncertainty, exit, and rollback.
ADOPT upstream already fits WRAP preserve upstream + add contract EXTRACT reuse one bounded seam or patch FORK sustainable evidenced divergence ALLY cooperate with exact maintainers DECLINE evidence or fit is insufficient
No social authority score.
Public contributor context may route research toward relevant technical work. Stars, follows, affiliations, popularity, or inferred personal traits do not establish competence, authority, trust, or governance power.