aman99dex/Obligo
Deployment-context-aware license compliance scan — fails the build on license obligations your deployment context actually triggers.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 9, 2026
- License
- MIT
Pinned Snippet
uses: aman99dex/obligo@b8d91e9b65c6e9b9c51881fbde4261de007802ae # v0.5.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| path | Directory to scan | — | . |
| context-file | Path to context.yaml describing how you deploy | — | context.yaml |
| fail-on | Findings at or above this severity fail the job: critical|warning|unknown|info|never | — | critical |
| strict | Also fail (exit 2) when any scanner was skipped or degraded | — | false |
| format | Output format: terminal|json|cyclonedx|sarif | — | terminal |
| output | File to write the report to (required for sarif upload) | — | "" |
| version | Obligo version to install (PyPI requirement spec) | — | obligo |
Outputs
no outputs