RedentialThe open-source CLI that proves what you can build. NDA-safe.
Turn private repos into a credential you can share and defend. Reads your local git history. Produces metadata, never code.
npx redential scanGetting a command not found error? alternative installation methods
What is Redential CLI?
Redential CLI is an open source tool that turns your private git history into a verifiable skills profile, without your code ever leaving your machine.
- Local only —
scanmakes zero network calls; nothing uploads without your explicit confirmation - Metadata, never code — languages, activity patterns, capabilities; never file names, commit messages, or source
- Exact payload review — see the byte-for-byte JSON before anything is sent
- Structural detection — recognizes connected patterns (webhook → DB write → idempotency), not just imports
- Provable privacy — every claim is an executable test in the repo, and releases ship with npm provenance
- Honest tiers — local evidence is labeled Attested, never Verified; defend it live to strengthen it
- No account needed —
npx @redential/cli scanruns instantly; you only log in to publish
Frequently asked questions
What is the Redential CLI?
An open-source command-line tool that reads your local git history and turns it into a metadata-only skills credential. One command to try it: npx redential scan. Nothing installs globally and nothing is uploaded.
Does my code get uploaded?
No. The bundle contains metadata only: aggregates, hashed identifiers, and capability slugs from a closed public vocabulary. You see the exact JSON before anything uploads, and every privacy claim is an executable test in the repo, not a promise. See Trust & privacy.
Do I need an account?
Not to scan. Scanning is fully local and needs no login. An account is only needed if you choose to submit your bundle to your Redential profile.
How much does the CLI cost?
The CLI is free forever and Apache-2.0 licensed. Redential the platform has a free tier (including one full live defense) and a Pro plan for volume and sharing features.
How is this different from connecting my repo with the GitHub App?
The GitHub App is for repos you can connect, and earns a stronger evidence tier because Redential can verify the repo directly. The CLI is for the repos you can't connect: employer and NDA work. It earns the Attested tier, clearly labeled as such, and the live defense is what makes it credible.
Can I run it on my employer's repository?
The CLI is designed for exactly that case: nothing from the code itself ever leaves your machine, only bounded metadata about your own activity, and the scan asks you to confirm you are authorized to analyze the repository. What your specific contract allows is between you and it; the boundary the CLI guarantees is that source code, file names and free text never travel.
What if AI wrote part of my code?
Then you are like most working developers now. The bundle carries honest, bounded signals about AI-assisted work (like agent co-authorship counts), and the live defense tests whether you can explain and stand behind what shipped, which is the part that matters.
Is it open source?
Yes, Apache-2.0, at github.com/Redential/redential-cli. The contribution we want most is people trying to break the trust model: red-teaming the detection signals is explicitly invited.