Repository navigation
Releases
tally v0.6.0
- tally is open source under the MIT licence. Public repositories can now use the action, and the README shows
how to install the CLI with Bun. - A dry run shows who each issue would be assigned to.
tally issues sync --dry-runaddsassigneeto every
planned create and edit in JSON, and-> HANDLEin text, so an owner handle orTALLY_ORG_ASSIGNEEcan be
checked before any issue is filed. - An entry can record a key nobody has created yet.
provisioned: false(ortally add ... --unprovisioned)
marks a credential the code reads but that does not exist. The variable counts as declared, andcheckreports no
expiry or limit gap and nomissinglocation for it. When a store holds a copy, aprovisionedgap asks for its
facts.
tally v0.5.0
-
Locations can be added to an existing key.
tally locate ID --location KIND:REFrecords another copy without
rewriting the entry by hand. -
The entry field table names
rotated.tally rotatedwrites the rotation date there, a key rotated elsewhere can
record it by hand,checkdoes not warn on it, and the key's issue shows it as the last rotation. -
Keys an organization owns can go to a person. Set the action's
org-assigneeinput, or
TALLY_ORG_ASSIGNEE, to a handle, and their issues are assigned to it with noorg-ownergap. A repository
that keeps personal handles out of its tree can pass it from a repository variable. -
An account name in a note no longer looks like a credential. The guard now splits text at
@too, so a
service account name such asreader@example-project-123456passes validation. -
The tally skill reviews every key. A new section walks an agent through coverage, missing facts, expiries
and limits the provider offers, and stale keys, so a cleancheckis not mistaken for an up-to-date registry. -
Agents can start with bare
tally. Outside a terminal it prints schema JSON, including the standard parser's option definitions. Interactive terminals open the dashboard. -
Run
tallyto open the dashboard. It opens at once from the tally file and fills in what the secret stores
report when they answer, so a slow store never holds the screen. Keys nest by group, then service, and every group
starts folded with a count of what its keys need, so an expiring key shows without opening it. A service with one
key is that key's row.enteror→opens a group,←folds it or goes to its parent, a filter opens every group,
andenteron a key shows its facts and findings below the list. The dashboard uses one dark palette in every
terminal, and a reload keeps the selected key.tally uiremains an alias. -
Secret stores are read at once.
check,notifyand the dashboard list every source and look up every owner in
parallel instead of one after another. -
CLI options use the standard parser. Options accept
--name=value, repeated locations and the--separator. -
A local Unix pass store is a source.
pass: LABEL(optionally with afiltername prefix) lists the entries under
PASSWORD_STORE_DIRor~/.password-storewith the modified time of each.gpgfile, from directory listings only:
nothing is decrypted or read. Names are case-sensitive, symlinks and a missing store fail the run, andinitnever
drafts or links a pass entry. The date is when the ciphertext changed, not proof of rotation. -
Google Cloud annotations carry credential facts.
tally-owner,tally-service,tally-expires,
tally-expires-note,tally-limitandtally-runbookfill an entry's unknown owner, service, expiry, limit and
runbook. Values in.tally.yamlwin, conflicting annotations fail the run, and nothing is written to the file. -
A Google Cloud secret's
expireTimeis no longer a credential expiry. It is the date Secret Manager deletes the
secret, and now raises adeletionfinding withinwarnDays, whatever the entry'sexpiressays. -
Draft facts are visible. Keys drafted by
tally initwithservice: unknownorowner: unknownnow show
unknown-serviceandunknown-ownergap findings. -
Help output is predictable. Commands still print JSON when stdout is not a terminal, while help and version print
text unless--jsonis given. -
Text output is aligned.
check,notifyandlistnow show headers with aligned columns, and notifications use
the same finding table as check output. -
User fallback errors explain the location. Outside a repository, a missing user-level tally file now names the
repository and gives thetally initandtally addnext steps. -
Organization owners are reported. Online checks look up owner types and report
org-ownerwhen a key cannot be
assigned to an organization, and issue sync stops trying to assign those keys. Lookup failures are ignored, and
validateremains a file-only offline check. -
Assignment failures are reported and retried. Issue sync includes assignment failures in its text and JSON output,
retries them on the next run, and continues with later writes. An edit that only retries the assignment is marked
assign only.
v0.4.1
v0.4.0
- GitHub secrets.
github: OWNER/NAMEreads a repository's Actions and environment secret names and update
dates, andgithub: ORGan organization's, throughgh. An Actions secret unchanged forstaleDaysis now
reported asstale, and an organization secret can be declared asgithub: ORG/NAME. - Exact GitHub scopes. A
githublocation matches only its own repository, environment or organization, so a
repository secret no longer stands in for an environment secret of the same name. Environment names may hold
slashes or other characters GitHub allows. - Fewer false workflow secrets. A job or step named
secrets(needs.secrets.result) is no longer read as a secret. - More credential names. Env templates also count names ending in
PASSPHRASE,PAT,KEYSTOREorHOOKas
credentials.
v0.3.0
- Provider key listings.
sources:reads Anthropic, OpenAI, OpenRouter and Cloudflare key listings through their
admin APIs, with the token from an environment variable. A provider's expiry and spend limit fill in an unknown one,
and its last-use date reports a key unused foridleDaysasidle. A provider that says a key never expires or has
no limit is reported as ano-expiryorno-limitgap. Requests are GET only, to that provider's own key listing
paths, with no redirects.
v0.2.0
- Terminal view.
tally uilists keys by urgency with the selected key's locations and findings beside it, and a
second list of every finding. It filters, sorts and reloads in place. initextends an existing file. Running it again adds store copies and new locations to the entry that already
names that secret, and drafts entries only for secrets nobody declared. A store name that is not credential-shaped is
never drafted.ignorePaths. Globs for files the workflow and env template scans skip, such as test fixtures.- Repeated settings are errors. A top-level setting written twice in
.tally.yamlused to let the last one win
silently; it is now reported byvalidateand every other command.
v0.1.0
First release.
- Secret stores.
sources:reads names and dates from Google Cloud Secret Manager, AWS Secrets Manager and Azure
Key Vault through their own CLIs, never values.checkreports a value unchanged forstaleDaysasstale, a
declared secret the store lacks asmissing, and a stored secret nobody declared asunregistered, and a store's
expiry fills in an unknown one.--offlineskips the stores for a quick check. - Keys found from the code. Credential-named variables in tracked env templates, commented out or not, count as keys the code reads,
next to the secrets workflows reference.tally initdrafts both, andcheckreports any nobody declared. Only
names are read, andcredentialNamesadds naming conventions. - One file per repository. Settings and keys live together in
.tally.yaml:warnDays,issueRepo,
secretPatterns,ignoreandkeys. Discovery isTALLY_CONFIG, then the nearest.tally.yamlup to the
repository root, then~/.config/tally/tally.yamlfor keys that live on one machine. A file can hold many keys, and
anidonly has to be unique within it. - Metadata, never values. Every entry records owner, service, optional group, locations, limit and expiry. No
value is ever read, written or printed, and the validator rejects text that looks like a credential, including
provider prefixes and long random-looking tokens. - Every entry names every copy. A location is
github:for this repository,env:scoped, orowner/repo/NAME
for another repository, and any other kind is an open slug. A new store needs an entry, not a code change. - The workflows are read, never run.
tally checkcompares the secrets.github/workflowsexpressions
reference against the declared entries. A secret a workflow reads but nobody declared is anunregistered
action finding; a declared Actions secret no workflow reads is anunusedone.ignorelists names that are not
credentials, andGITHUB_TOKENis always skipped. - Start from what exists.
tally initwrites.tally.yamlwith a draft entry per referenced secret, so the facts
to fill in are the ones the repository already depends on. - Expiry is checked, missing facts are tracked.
tally checkexits 3 for expired keys and keys inside the warning
window. A key with no recorded expiry or limit is a gap, which never blocks a check but is visible in the digest. - A daily issue pass.
tally issues synccreates one issue per action finding, keeps one digest for gaps, edits
issues as dates move and closes them when the finding clears. Each entry's issue is assigned to its owner, and stays
unassigned if gh rejects the owner. With no repository named, gh infers it from the working
directory. - A composite action.
uses: OWNER/tally@v1runsissues syncwith the workflow's own token, so a consuming
repository adds no tooling and needs onlyissues: write. - Desktop notifications.
tally notifyruns the same check and sends onenotify-sendmessage per action finding,
for a timer on a machine that holds keys. - Agents first.
tally check --jsonfor findings,tally schemafor the contract, exit codes 0, 1, 2 and 3 that
name the next step, and machine-readable output when piped. - Facts are filled in, never invented.
expires: unknownmeans nobody has looked,noneneeds a written reason,
and a key can carry the provider's own label plus its redacted fingerprint, at most 6 characters, so two keys with
the same name can be told apart. - Runbooks belong to the user.
runbookpoints at a path or URL in the repository that declares the key. The tool
ships no provider-specific steps.