hardenlabs/Harden Build Attestation
Attest a CI/CD build with Harden using OIDC — makes leaked credentials provably insufficient
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| client-id | Harden OAuth client ID | yes | — |
| client-secret | Harden OAuth client secret | yes | — |
| service-id | Harden service ID (svc_xxxx) | yes | — |
| api-endpoint | Harden API endpoint | no | https://api.hardenapi.com |
| token-endpoint | Override OAuth token endpoint (e.g., direct Cognito URL) | no | — |
| commit-sha | Override commit SHA (defaults to current commit) | no | — |
| max-retries | Max retry attempts for attestation API call | no | 3 |
| inject | Auto-inject build key into SDK source files (true/false). Searches for %%HARDEN_BUILD_KEY%% placeholders. | no | true |
| search-path | Directory to search for SDK placeholder files (default: current directory) | no | . |
Outputs
| name | description |
|---|---|
| build-key | The build attestation key (also injected into SDK if inject=true) |
| commit-sha | The commit SHA used for attestation |
| injected-files | Number of files where placeholders were replaced |