Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for advanced developers, researchers, and audit-minded teams that want evidence-linked diffs of how agent behavior changes across releases.
Who should use it
Who should skip it
Skip WEIFENG2333/phistory if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
WEIFENG2333/phistory is tracked by RepoRadar as a prompt archive in the Security & Evaluation section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. WEIFENG2333/phistory leads on workflow potential (9.1) and open-source/build quality (8.4); its lowest signal is momentum (6.0), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned WEIFENG2333/phistory a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 35.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Reproducing captures locally installs exact CLI packages and intercepts prompt-bearing requests, so do that in a controlled environment rather than inside a sensitive production setup; The archive reflects shipped client-side prompt artifacts and traces, not every server-side provider behavior, so treat it as strong client evidence rather than a complete behavioral proof.