pax_global_header 0000666 0000000 0000000 00000000064 15106255771 0014523 g ustar 00root root 0000000 0000000 52 comment=5b922d8cdd1050f9a6cb2be4efb45f558d5e0940 stac-validator-3.10.2/ 0000775 0000000 0000000 00000000000 15106255771 0014523 5 ustar 00root root 0000000 0000000 stac-validator-3.10.2/.dockerignore 0000664 0000000 0000000 00000000527 15106255771 0017203 0 ustar 00root root 0000000 0000000 __pycache__ *.pyc *.pyo *.pyd .Python env pip-log.txt pip-delete-this-directory.txt .tox .coverage .coverage.* .cache nosetests.xml coverage.xml *,cover *.log .git *.swp package-lock.json __pycache__ .pytest_cache .env .venv *.egg-info # CDK asset staging directory .cdk.staging cdk.out **/cdk.out/ **/.cdk.staging/ **/.direnv **/__pycache__/ stac-validator-3.10.2/.flake8 0000664 0000000 0000000 00000000302 15106255771 0015671 0 ustar 00root root 0000000 0000000 [flake8] max-line-length = 90 select = C,E,F,W,B,B950 max-complexity = 5 # Error Codes: http://pycdestyle.pycqa.org/en/latest/intro.html#configuration ignore = E501,C901,W503,E302 exclude = lib stac-validator-3.10.2/.github/ 0000775 0000000 0000000 00000000000 15106255771 0016063 5 ustar 00root root 0000000 0000000 stac-validator-3.10.2/.github/workflows/ 0000775 0000000 0000000 00000000000 15106255771 0020120 5 ustar 00root root 0000000 0000000 stac-validator-3.10.2/.github/workflows/docs.yml 0000664 0000000 0000000 00000003205 15106255771 0021573 0 ustar 00root root 0000000 0000000 name: Documentation on: push: branches: [ main ] paths: - 'docs/**' - 'stac_validator/**/*.py' - 'README.md' pull_request: branches: [ main ] paths: - 'docs/**' - 'stac_validator/**/*.py' - 'README.md' # Allow manual triggering workflow_dispatch: jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Set up Python uses: actions/setup-python@v4 with: python-version: '3.8' - name: Install dependencies run: | python -m pip install --upgrade pip pip install -e . pip install sphinx sphinx_rtd_theme myst-parser sphinx-autodoc-typehints - name: Build documentation run: | sphinx-build -b html docs/ docs/_build/html - name: Upload documentation artifact uses: actions/upload-artifact@v4 with: name: documentation path: docs/_build/html retention-days: 7 # Only deploy when pushing to main (not on PRs) deploy: needs: build if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'workflow_dispatch' runs-on: ubuntu-latest permissions: contents: write steps: - name: Download built documentation uses: actions/download-artifact@v4 with: name: documentation path: ./docs-build - name: Deploy to GitHub Pages uses: peaceiris/actions-gh-pages@v3 with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir: ./docs-build force_orphan: true commit_message: "Update documentation [skip ci]" stac-validator-3.10.2/.github/workflows/publish.yml 0000664 0000000 0000000 00000001435 15106255771 0022314 0 ustar 00root root 0000000 0000000 name: Publish on: push: tags: - "v*.*.*" # Triggers when a tag starting with 'v' followed by version numbers is pushed jobs: build-and-publish: name: Build and Publish to PyPI runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Set up Python 3.10 uses: actions/setup-python@v5 with: python-version: "3.10" - name: Install dependencies run: | python -m pip install --upgrade pip pip install setuptools wheel twine build - name: Build package run: | python -m build - name: Publish package to PyPI env: TWINE_USERNAME: "__token__" TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }} run: | twine upload dist/* stac-validator-3.10.2/.github/workflows/test-runner.yml 0000664 0000000 0000000 00000001655 15106255771 0023140 0 ustar 00root root 0000000 0000000 name: Test Runner on: push: branches: - main - dev pull_request: branches: - main - dev jobs: test: name: Execute tests runs-on: ubuntu-latest strategy: matrix: python-version: ["3.8", "3.9", "3.10", "3.11", "3.12", "3.13"] steps: - uses: actions/checkout@v2 - name: Set up Python ${{ matrix.python-version }} uses: actions/setup-python@main with: python-version: ${{ matrix.python-version }} - name: Run mypy if: matrix.python-version == '3.12' run: | pip install . pip install -e .[dev] mypy stac_validator/ - name: Run pre-commit if: matrix.python-version == 3.12 run: | pre-commit install pre-commit autoupdate pre-commit run --all-files - name: Run tox run: | pip install tox tox -e py stac-validator-3.10.2/.gitignore 0000664 0000000 0000000 00000002515 15106255771 0016516 0 ustar 00root root 0000000 0000000 # Byte-compiled / optimized / DLL files __pycache__/ *.py[cod] *$py.class # C extensions *.so # Distribution / packaging .Python build/ develop-eggs/ dist/ downloads/ eggs/ .eggs/ lib/ lib64/ parts/ sdist/ var/ wheels/ *.egg-info/ .installed.cfg *.egg MANIFEST # PyInstaller # Usually these files are written by a python script from a template # before PyInstaller builds the exe, so as to inject date/other infos into it. *.manifest *.spec # Installer logs pip-log.txt pip-delete-this-directory.txt # Unit test / coverage reports htmlcov/ .tox/ .coverage .coverage.* .cache nosetests.xml coverage.xml *.cover .hypothesis/ .pytest_cache/ # Translations *.mo *.pot # Django stuff: *.log local_settings.py db.sqlite3 # Flask stuff: instance/ .webassets-cache # Scrapy stuff: .scrapy # Sphinx documentation docs/_build/ # PyBuilder target/ # Jupyter Notebook .ipynb_checkpoints # pyenv .python-version # celery beat schedule file celerybeat-schedule # SageMath parsed files *.sage.py # Environments .env .venv env/ venv/ ENV/ env.bak/ venv.bak/ # Spyder project settings .spyderproject .spyproject # Rope project settings .ropeproject # mkdocs documentation /site # mypy .mypy_cache/ .envrc .idea/ .DS_Store # lambda file *.zip # IDE .vscode cdk-deployment/lambda/stac_validator/ cdk-deployment/build-libraries/libraries.zip Pipfile* stac-validator-3.10.2/.pre-commit-config.yaml 0000664 0000000 0000000 00000001342 15106255771 0021004 0 ustar 00root root 0000000 0000000 repos: - repo: https://github.com/PyCQA/flake8 rev: 7.0.0 hooks: - id: flake8 - repo: https://github.com/timothycrosley/isort rev: 5.13.2 hooks: - id: isort args: ["--profile", "black"] - repo: https://github.com/psf/black rev: 24.1.1 hooks: - id: black # language_version: python3.11 - repo: https://github.com/pre-commit/mirrors-mypy rev: v1.8.0 hooks: - id: mypy exclude: /tests/ # --strict args: [ --no-strict-optional, --ignore-missing-imports, --implicit-reexport, --explicit-package-bases, ] additional_dependencies: ["types-attrs", "types-requests"] stac-validator-3.10.2/.readthedocs.yml 0000664 0000000 0000000 00000000137 15106255771 0017612 0 ustar 00root root 0000000 0000000 # Build documentation in the docs/ directory with Sphinx sphinx: configuration: docs/conf.py stac-validator-3.10.2/CHANGELOG.md 0000664 0000000 0000000 00000040663 15106255771 0016345 0 ustar 00root root 0000000 0000000 # STAC Validator Change Log All notable changes to this project will be documented in this file. The format is (loosely) based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to [Semantic Versioning](http://semver.org/). ## [Unreleased] ## [v3.10.2] - 2025-11-16 ### Fixed - Added validation for STAC version format to provide clear error messages when stac_version field is missing, empty, or incorrectly formatted (e.g., "1.1" instead of "1.1.0"). [#268](https://github.com/stac-utils/stac-validator/pull/268) ### Changed - Migrated from `setup.py` to modern `pyproject.toml` packaging (PEP 621), removing legacy `requirements-dev.txt` file. [#268](https://github.com/stac-utils/stac-validator/pull/268) ## [v3.10.1] - 2025-07-26 ### Fixed - Reverted path cleaning changes that removed `./` prefix from relative paths, which was causing compatibility issues with tools like stac-check. The validator now correctly preserves the `./` prefix for relative paths in the current directory. [#266](https://github.com/stac-utils/stac-validator/pull/266) ## [v3.10.0] - 2025-07-20 ### Added - Added detailed recursive validation summary showing validation counts by STAC object type (Catalog, Collection, etc.) [#265](https://github.com/stac-utils/stac-validator/pull/265) - Added validation duration timing that shows total processing time in a human-readable format [#265](https://github.com/stac-utils/stac-validator/pull/265) - Added support for pydantic validation in recursive mode with proper schema reporting [#265](https://github.com/stac-utils/stac-validator/pull/265) ### Changed - Standardized summary output formatting across all validation modes for consistency [#265](https://github.com/stac-utils/stac-validator/pull/265) ## [v3.9.3] - 2025-06-28 ### Changed - Improved path resolution in recursive validation to handle relative paths more reliably, especially in GitHub repository structures [#264](https://github.com/stac-utils/stac-validator/pull/264) ### Fixed - Fixed issue where validator would get confused by repository structure when validating catalogs with relative paths [#264](https://github.com/stac-utils/stac-validator/pull/264) - Cleaned up path output by removing unnecessary `./` components from displayed paths [#264](https://github.com/stac-utils/stac-validator/pull/264) ### Removed ## [v3.9.2] - 2025-06-18 ### Fixed - Fixed missing item id in the url path with --item-collection output [#263](https://github.com/stac-utils/stac-validator/pull/263) ## [v3.9.1] - 2025-06-13 ### Added - `failed_schema` field to error messages for easier error handling [#260](https://github.com/stac-utils/stac-validator/pull/260) - `recommendation` field to --verbose mode [#260](https://github.com/stac-utils/stac-validator/pull/260) ## [v3.9.0] - 2025-06-13 ### Added - Added separate `recommendation` field in error messages when running in non-verbose mode [#257](https://github.com/stac-utils/stac-validator/pull/257) - Verbose error messages for JSONSchemaValidationErrors [#257](https://github.com/stac-utils/stac-validator/pull/257) ### Changed - Changed --verbose for recursive mode to --trace-recursive to make way for more comprehensive error messaging [#257](https://github.com/stac-utils/stac-validator/pull/257) ## [v3.8.1] - 2025-06-04 ### Fixed - Fixed the pydantic extra dependency in setup.py to properly install stac-pydantic when using `pip install stac-validator[pydantic]` [#254](https://github.com/stac-utils/stac-validator/pull/254) ## [v3.8.0] - 2025-06-03 ### Added - Added `--schema-config` option to specify a YAML or JSON configuration file that maps remote schema URLs to local file paths, making it easier to validate against multiple local schemas, allowing offline validation and improved performance [#253](https://github.com/stac-utils/stac-validator/pull/253) ## [v3.7.0] - 2025-05-30 ### Added - Added a comprehensive Table of Contents to README.md [#247](https://github.com/stac-utils/stac-validator/pull/247) - Added Sponsors and Supporters section to README.md with organizational logos and acknowledgments [#247](https://github.com/stac-utils/stac-validator/pull/247) - Added `--pydantic` option for validating STAC objects using stac-pydantic models, providing enhanced type checking and validation [#249](https://github.com/stac-utils/stac-validator/pull/249) - Added optional dependency for stac-pydantic that can be installed with `pip install stac-validator[pydantic]` [#249](https://github.com/stac-utils/stac-validator/pull/249) - Added GitHub Actions workflow for automatically building and deploying documentation to GitHub Pages [#250](https://github.com/stac-utils/stac-validator/pull/250) ### Changed - Reformatted and restructured the README.md for improved readability and organization [#247](https://github.com/stac-utils/stac-validator/pull/247) - Migrated documentation from Read the Docs to GitHub Pages for better integration with the repository [#250](https://github.com/stac-utils/stac-validator/pull/250) - Updated documentation system to use Sphinx with MyST parser for improved Markdown support [#250](https://github.com/stac-utils/stac-validator/pull/250) - Enhanced documentation to include content directly from README.md for consistency [#250](https://github.com/stac-utils/stac-validator/pull/250) ## [v3.6.0] - 2025-03-25 ### Added - If a validation error occurs in recursive mode only show the invalid items unless verbose mode is on. [#243](https://github.com/stac-utils/stac-validator/pull/243) - Added ability to validate extensions of Collections [#243](https://github.com/stac-utils/stac-validator/pull/243) - Improve error reporting through use of [best_match](https://python-jsonschema.readthedocs.io/en/stable/errors/#best-match-and-relevance) [#243](https://github.com/stac-utils/stac-validator/pull/243) - Add `schema-map` option similar to [stac-node-validator SchemaMap](https://github.com/stac-utils/stac-node-validator?tab=readme-ov-file#usage) to allow validation against local copies of schemas. [#243](https://github.com/stac-utils/stac-validator/pull/243) ## [v3.5.0] - 2025-01-10 ### Added - Added publish.yml to automatically publish new releases to PyPI [#236](https://github.com/stac-utils/stac-validator/pull/236) - Configure whether to open URLs when validating assets [#238](https://github.com/stac-utils/stac-validator/pull/238) - Allow to provide HTTP headers [#239](https://github.com/stac-utils/stac-validator/pull/239) ### Changed - Switched to the referencing library for dynamic JSON schema validation and reference resolution [#241](https://github.com/stac-utils/stac-validator/pull/241) ## [v3.4.0] - 2024-10-08 ### Added - Added ability to validate response from a /collections endpoint [#220](https://github.com/stac-utils/stac-validator/issues/220) - Added mypy to pre-commit config ([#229](https://github.com/stac-utils/stac-validator/pull/224)) - Support for stac spec version 1.1.0 [#235](https://github.com/stac-utils/stac-validator/pull/235) ## [v3.3.2] - 2023-11-17 ### Added - Docstrings ([#224](https://github.com/stac-utils/stac-validator/pull/224)) ### Changed - Development dependencies removed from runtime dependency list ([#228](https://github.com/stac-utils/stac-check/pull/109)) - Remove jsonschema RefResolver ([#228](https://github.com/stac-utils/stac-check/pull/109) ## [v3.3.1] - 2022-12-16 ### Fixed - Moved --verbose messaging for --recursive as --verbose was printing out the wrong messages https://github.com/stac-utils/stac-validator/pull/222 ## [v3.3.0] - 2022-11-28 ### Added - Added --item-collection to validate local and remote item collections https://github.com/stac-utils/stac-validator/pull/219 - Added --pages to validate additional items retrieved via pagination links https://github.com/stac-utils/stac-validator/pull/219 ## [v3.2.0] - 2022-09-20 ### Added - Added ability to check local schemas in item extensions https://github.com/stac-utils/stac-validator/pull/215 - Added an example on validating a dictionary https://github.com/stac-utils/stac-validator/pull/215 ### Changed - Changed 'ValidationError' error type to 'JSONSchemaValidationError' https://github.com/stac-utils/stac-validator/pull/213 ## [v3.1.0] - 2022-04-28 ### Added - Added update stac version message to cli output https://github.com/stac-utils/stac-validator/pull/211 ### Fixed - Reordered exception handlers to avoid unreachable code https://github.com/stac-utils/stac-validator/pull/203/ - Details about invalid items are shown in the message when in recursive mode https://github.com/stac-utils/stac-validator/pull/202/ - Dockerfile - change cli command from stac_validator to stac-validator https://github.com/stac-utils/stac-validator/pull/201/ - Items with no assets key can still be valid https://github.com/stac-utils/stac-validator/pull/206 - Top-level `is_valid` flag for recursive JSONSchema exceptions https://github.com/stac-utils/stac-validator/pull/208 ### Removed - Stac-check linting as it creates a circular dependency https://github.com/stac-utils/stac-validator/pull/209 - Remove v0.7.0 test data and v0.7.0 local tests https://github.com/stac-utils/stac-validator/pull/210 - Removed pystac from dependencies https://github.com/stac-utils/stac-validator/pull/210 ## [v3.0.0] - 2022-03-11 ### Added - A note about full recursion to the `--max-depth` help text ### Fixed - Item messages are now included even if `max_depth is None` - Exit with non-zero code when validation fails ### Removed - References to Python 3.6 ## [v2.5.0] - 2022-03-10 ### Changed - Split the `--recursive` option into a `--recursive` flag and a `--max-depth` option - Renamed the entry point from `stac_validator` to `stac-validator` ## [v2.4.3] - 2022-03-10 ### Changed - Add schema caching ## [v2.4.2] - 2022-03-02 ### Changed - Loosen pystac version dependency ## [v2.4.1] - 2022-03-02 ### Changed - Loosen stac-check version dependency ## [v2.4.0] - 2022-02-02 ### Added - Linting option in cli to display stac-check generated information ## [v2.3.0] - 2021-08-31 - 2021-11-28 ### Added - Added --links option to validate links on format and a valid response - Added --assets option to validate assets on format and and a valid response - Added test_links.py - Added v1.0.0 STAC examples from radiant earth github - Added v1.0.0 examples to tests ### Changed - Upgraded pystac to 1.1.0 from 0.5.6 - Moved tests for cli options out of test_stac_validator into individual files - Moved utilities to utilities.py - Moved backend to validate.py ## [v2.2.0] - 2021-05-25 ### Added - Added Support for STAC 1.0.0 - Added more tests for STAC 1.0.0-rc.4 - Option to pass stac dictionary into validator in python with new stac_dict method ### Changed - Moved std out to cli so that it doesn't display in pure python applications - Added Pypi badges to readme ## [v2.1.0] - 2021-05-06 ### Added - Added more tests for STAC 1.0.0-rc.3 - Added basic support for rc.4 - Add system exit code to CLI. see #144 ### Changed - Modified how Lambda CDK is built ## [v2.0.0] - 2021-04-28 ### Added - Stac versions from 0.8.0 --> 1.0.0-rc.3 are now supported. - Version is detected automatically. - Default validation attempts to validate a core Stac object as well as any extensions. - Recursion which was previously handled by Pystac is now done natively with both a depth option to limit the time it takes to validate and a verbose option to display output as individual objects are being validated one by one. - Added AWS CDK deployment example. - Added FastAPI routing to CDK deployment. ### Changed - Pystac is now only being used to identify stac objects. Jsonschema is being used for all other validation. - The cli library was changed from Docopt to Click. - Custom validation was updated to allow for local schemas. ### Removed - The force, legacy, version, and update methods were removed. - stac versions where a `stac_version` field is not present are no longer supported. ## [v1.0.1] - 2020-09-01 ### Added - The ability (--update) to update a STAC object. This is based on migrate from pystac. It doesn't always work. Frequently it does. Presently it tries to update to version 1.0.0-beta.2 - A function to display what has changed via --update. This is represented in the logs as diff. - A --force option. This updates the stac_version to v0.9.0 and adds an id field as older STAC versions seem to be missing this sometimes. This seems to be especially effective with objects as old as 0.6.0 and 0.6.1 - An option (--version) to specify and set a specific version to validate against. - The --extension option. This uses pystac validation to validate against various extension schemas. - The ExtensionError, as inputing a bad value for extension caused validation in pystac to be bypassed. - The VersionError, as inputing a bad value for version was causing validation in pystac to be bypassed as well. - The --recursive option. This uses validate_all from pystac to recursively search the links from a catalog or collection. - The ability (--core) to validate against the core only. This is provided by pystac. - (--legacy). This validates agains schemas from v0.4.0 to v1.0.0-beta.1 Legacy must be accompanied by --version. - valid_versions for --legacy are: 'v0.4.0', 'v0.4.1', 'v0.5.0', 'v0.5.1', 'v0.5.2', 'v0.6.0', 'v0.6.0-rc1', 'v0.6.0-rc2', 'v0.6.1', 'v0.6.2', 'v0.7.0', 'v0.8.0', 'v0.8.0-rc1', 'v0.8.1', 'v0.9.0', 'v0.9.0-rc1', 'v0.9.0-rc2', and 'v1.0.0-beta.1' - (--custom). Validate against a custom schema - Tests to explore new functionality. ### Changed - Updated core validation to use validation from pystac instead of jsonchema. - With the newest version - 1.0.0-beta.2 - items will run through jsonchema validation before the PySTAC validation. The reason for this is that jsonschema will give more informative error messages. This should be addressed better in the future. This is not the case with the --recursive option as time can be a concern here with larger collections. - Logging. Various additions were made here depending on the options selected. This was done to help assist people to update their STAC collections. [Unreleased]: https://github.com/sparkgeo/stac-validator/compare/v3.10.2..main [v3.10.2]: https://github.com/sparkgeo/stac-validator/compare/v3.10.1..v3.10.2 [v3.10.1]: https://github.com/sparkgeo/stac-validator/compare/v3.10.0..v3.10.1 [v3.10.0]: https://github.com/sparkgeo/stac-validator/compare/v3.9.3..v3.10.0 [v3.9.3]: https://github.com/sparkgeo/stac-validator/compare/v3.9.2..v3.9.3 [v3.9.2]: https://github.com/sparkgeo/stac-validator/compare/v3.9.1..v3.9.2 [v3.9.1]: https://github.com/sparkgeo/stac-validator/compare/v3.9.0..v3.9.1 [v3.9.0]: https://github.com/sparkgeo/stac-validator/compare/v3.8.1..v3.9.0 [v3.8.1]: https://github.com/sparkgeo/stac-validator/compare/v3.8.0..v3.8.1 [v3.8.0]: https://github.com/sparkgeo/stac-validator/compare/v3.7.0..v3.8.0 [v3.7.0]: https://github.com/sparkgeo/stac-validator/compare/v3.6.0..v3.7.0 [v3.6.0]: https://github.com/sparkgeo/stac-validator/compare/v3.5.0..v3.6.0 [v3.5.0]: https://github.com/sparkgeo/stac-validator/compare/v3.4.0..v3.5.0 [v3.4.0]: https://github.com/sparkgeo/stac-validator/compare/v3.3.2..v3.4.0 [v3.3.2]: https://github.com/sparkgeo/stac-validator/compare/v3.3.1..v3.3.2 [v3.3.1]: https://github.com/sparkgeo/stac-validator/compare/v3.3.0..v3.3.1 [v3.3.0]: https://github.com/sparkgeo/stac-validator/compare/v3.2.0..v3.3.0 [v3.2.0]: https://github.com/sparkgeo/stac-validator/compare/v3.1.0..v3.2.0 [v3.1.0]: https://github.com/sparkgeo/stac-validator/compare/v3.0.0..v3.1.0 [v3.0.0]: https://github.com/sparkgeo/stac-validator/compare/v2.5.0..v3.0.0 [v2.5.0]: https://github.com/sparkgeo/stac-validator/compare/v2.4.3..v2.5.0 [v2.4.3]: https://github.com/sparkgeo/stac-validator/compare/v2.3.0..v2.4.0 [v2.4.2]: https://github.com/sparkgeo/stac-validator/compare/v2.4.1..v2.4.2 [v2.4.1]: https://github.com/sparkgeo/stac-validator/compare/v2.4.0..v2.4.1 [v2.4.0]: https://github.com/sparkgeo/stac-validator/compare/v2.3.0..v2.4.0 [v2.3.0]: https://github.com/sparkgeo/stac-validator/compare/v2.2.0..v2.3.0 [v2.2.0]: https://github.com/sparkgeo/stac-validator/compare/v2.1.0..v2.2.0 [v2.1.0]: https://github.com/sparkgeo/stac-validator/compare/v2.0.0..v2.1.0 [v2.0.0]: https://github.com/sparkgeo/stac-validator/compare/v1.0.1..v2.0.0 [v1.0.1]: https://github.com/sparkgeo/stac-validator/compare/v0.5.0..v1.0.1 [v0.5.0]: https://github.com/sparkgeo/stac-validator/compare/v0.1.3..v0.5.0 [v0.1.3]: https://github.com/sparkgeo/stac-validator/compare/v0.1.1..v0.1.3 [v0.1.1]: https://github.com/sparkgeo/stac-validator/compare/v0.1.0..v0.1.1 [v0.1.0]: https://github.com/sparkgeo/stac-validator/releases/tag/v0.1.0 stac-validator-3.10.2/Dockerfile 0000664 0000000 0000000 00000000211 15106255771 0016507 0 ustar 00root root 0000000 0000000 FROM python:3.8-slim-buster WORKDIR /code COPY . /code/ RUN pip install . && \ stac-validator --help ENTRYPOINT ["stac-validator"] stac-validator-3.10.2/LICENSE 0000664 0000000 0000000 00000026112 15106255771 0015532 0 ustar 00root root 0000000 0000000 Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2019 Sparkgeo Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. stac-validator-3.10.2/Makefile 0000664 0000000 0000000 00000001513 15106255771 0016163 0 ustar 00root root 0000000 0000000 help: ## Show this help @fgrep -h "##" $(MAKEFILE_LIST) | fgrep -v fgrep | sed -e 's/\\$$//' | sed -e 's/##//' install: ## Install using pip pip install . install-edit: ## Install using pip in edit mode pip install --editable .["test"] code-check: ## Check and format code using pre-commit pre-commit install pre-commit autoupdate pre-commit run --all-files test: ## Run the tests pytest --verbose pytest --mypy stac_validator build-docker: ## Build a Docker container docker build -t stac-validator . build-tox: ## Test stac_validator on multiple Python versions docker build -f tox/Dockerfile-tox -t stac_tox . run: ## Run the Docker Container and enter into bash docker run -it --entrypoint /bin/bash stac-validator docs: ## Build documentation locally sphinx-build -b html -E docs/ docs/_build/html stac-validator-3.10.2/README.md 0000664 0000000 0000000 00000042651 15106255771 0016012 0 ustar 00root root 0000000 0000000 # SpatioTemporal Asset Catalog Validator