overturemaps/stac-check-action

Run stac-check on local STAC files

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
stac-check-versionstac-check PyPI version (e.g., 1.9.1 or v1.9.1; leading "v" stripped) or "latest"yes
filePath to local STAC file to validateyes
recursiveRecursively validate related local STAC objectsnofalse
max-depthMaximum recursion depth (requires recursive: true)no""
validate-assetsValidate assets locally (no network requests)nofalse
pydanticUse stac-pydantic for enhanced validationnofalse
verboseShow verbose error messagesnofalse
fastFast validation with FastJSONSchema, no geometry/lintingnofalse
fast-lintingFast validation with linting, no geometry checksnofalse
output-fileSave CLI output to file (requires recursive: true per stac-check CLI)no""
job-summaryWrite validation results to GitHub job summarynotrue
comment-prPost validation summary as PR comment (requires pull-requests: write)nofalse
extra-argsAdditional stac-check CLI arguments (appended last)no""
configPath to config file or inline YAML (sets STAC_CHECK_CONFIG env var)no""
namedescription
exit-codeRaw stac-check CLI exit code. Note: not authoritative for recursive validation — check `valid` instead, since stac-check often returns 0 even when recursive validation fails.
log-pathPath to captured stac-check stdout/stderr. Set on every successful invocation of the runner (created before input validation, so available even on early-exit errors).
validAuthoritative validation result: `true` if no failure markers were found in the stac-check output, `false` otherwise.