API keys, their use and when they expire. Sample data: seven keys from Sep 16 to Nov 14, rotation on Sat 24, prod-runtime at 1.2M calls in 30 days.
Installation
- 1
Set up the registry once
Your token in .env and @chartory in components.json. Skip this when another chart is already installed.
Installation guide - 2
Add the chart
One command adds the Key timeline component to your project.
npx shadcn add @chartory/key-timeline - 3
Use it
Pass your rows. The props are the Figma properties.
usage.tsximport { KeyTimeline } from "@/components/chartory/key-timeline"<KeyTimeline data={apiKeys} size="m" legend/>
Props
<KeyTimeline>
Every prop but data is a Figma property with the same name and values.
KeyTimelineData
The data prop: one object for the whole chart.
KeyTimelineLane
One object per entry in keys.
KeyTimelineRotate
The rotate object.
The data as a JSON Schema: schemas/key-timeline.json
Key timeline: a React and Figma chart in four sizes
What does a key timeline show?
A key timeline gives each API key a lane with its calls per day, its expiry and planned rotations, and flags keys used from a new network. Use it for key rotation, secrets reviews and access audits.
Chartory ships it as a Figma component and a React component with the same name. The code installs from the shadcn registry with one command and lands in your project as a file you own.
What is the Key timeline component?
It is one <KeyTimeline> component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is keys with use per day, expiry and events.
Sizes XS, S, M and L re-lay the chart out from the data instead of scaling it, so labels stay readable at every size.
When should I use it?
- Is it keys over time? Yes means the key timeline fits.
- Do expiry dates matter? Yes means the key timeline fits.
- Is it keys, not sessions? Yes means the key timeline fits.
When does another type fit better?
- What one key can reach. Use Reach tree instead.
- Plain usage. Use Horizontal bars instead.
- Signed-in devices. Use Session lanes instead.
Key timeline questions
Installing, data, Figma and plans.
Yes. It installs through the shadcn registry with the shadcn CLI, and the file lands in your project.
Add your token and the @chartory registry once, then run npx shadcn add @chartory/key-timeline. The Installation guide has the steps.
Yes. Connect the Chartory MCP server and ask for the key timeline chart; the agent runs the same command and you review the diff.
Keys with use per day, expiry and events. The sample data comes with the component, and the props table lists every field.
XS, S, M and L, in Figma and in code. Each size is laid out again from the data, so text and lines keep their size.
Yes. chart/120-key-timeline has the same properties as the component.
Yes. Every paint is a token, so the chart follows light and dark mode and the collection you pick.
Code and Complete. Figma has the Figma file only.