Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want a git-native Postman alternative and a safer way to let coding agents hit real APIs through curated requests instead of guessed curl snippets.
Who should use it
Who should skip it
Consider jtaoufik/tiger lower priority if you already have a working solution in this category.
About this signal
jtaoufik/tiger is tracked by RepoRadar as a developer tool in the API Tooling section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, jtaoufik/tiger is strongest on workflow potential (9.1) and open-source/build quality (8.4) and weakest on momentum (6.0) — a profile worth weighing against your own priorities. 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 jtaoufik/tiger 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 59.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
The MCP run_request flow can hit real endpoints with saved auth and chained variables, so point assistants at staging or read-only collections first; Environment files, auth data, and client certificates live in the local workspace, so treat the collection folder like code plus credentials; The desktop builds are not yet code-signed on macOS per the README, so verify release artifacts before installing outside a test machine.