step-security/esigner-codesign
GitHub Action for SSL.com code signing with enhanced security features
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| command | Signing command to execute | yes | --version |
| username | SSL.com account username for authentication | no | — |
| password | SSL.com account password (recommend using secrets) | no | — |
| credential_id | Unique identifier for the signing certificate credential | no | — |
| totp_secret | Time-based one-time password secret for two-factor authentication | no | — |
| program_name | Program or application name for signing metadata | no | — |
| file_path | Absolute path to the single file to be signed | no | — |
| dir_path | Directory path containing multiple files for batch signing | no | — |
| output_path | Destination directory where signed artifacts will be saved | no | — |
| malware_block | Enable malware scanning before signing to prevent compromised code (true/false) | no | — |
| override | Replace the original file with signed version instead of creating new file (true/false) | no | — |
| clean_logs | Remove log files after signing operation completes (true/false) | no | false |
| environment_name | Target environment for signing operations (PROD for production, TEST for sandbox) | no | PROD |
| jvm_max_memory | Maximum Java Virtual Machine heap memory allocation (e.g., 1024M, 2048M) | no | 1024M |
| signing_method | Code signing implementation version to use (v1 or v2) | no | v1 |
Outputs
no outputs