Documentation Index
Fetch the complete documentation index at: https://code.storage/docs/llms.txt
Use this file to discover all available pages before exploring further.
Repository management
Code Storage repositories are identified by unique IDs. You can either let the system generate an ID
or provide your own:
// Auto-generated ID
const repo = await store.createRepo();
console.log(repo.id); // e.g., '123e4567-e89b-12d3-a456-426614174000'
// Custom ID with namespacing
const customRepo = await store.createRepo({ id: 'team/project-alpha' });
console.log(customRepo.id); // 'team/project-alpha'
/ for organizing repositories by team, project, or user.
Authentication & Security
All access to Code Storage requires JWT tokens signed by your organization. Each token:
- Grants access to a single repository (except
org:read tokens, which are org-wide)
- Contains explicit permission scopes
- Has a configurable time-to-live (TTL)
- Is customer-signed for full control
The SDK helps simplify and automate the management of these tokens.
Token structure
{
"iss": "your-org", // Your organization identifier
"sub": "ci-pipeline-prod", // Agent identity (for logging)
"repo": "team/project-alpha", // Repository access
"scopes": ["git:read", "git:write"], // Permissions
"iat": 1723453189, // Issued at (Unix timestamp)
"exp": 1723456789 // Expiration (Unix timestamp)
}
{
"alg": "ES256", // Algorithm (ES256 or RS256 are supported)
"typ": "JWT", // Type
}
Permission scopes
| Scope | Description | Operations |
|---|
git:read | Read repository contents | clone, fetch, pull |
git:write | Modify repository | push (includes read) |
repo:write | Create repositories | POST /api/v1/repos |
org:read | List repositories | GET /api/v1/repos |
Key management
Public keys for JWT verification are managed through the Pierre Admin Panel.
For detailed authentication setup, manual JWT generation, and advanced token configuration, see Authentication.