ocsf-schema-compiler 0.9.2__tar.gz

ocsf_schema_compiler-0.9.2/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

ocsf_schema_compiler-0.9.2/PKG-INFO

@@ -0,0 +1,130 @@
+Metadata-Version: 2.4
+Name: ocsf-schema-compiler
+Version: 0.9.2
+Summary: Compile an Open Cybersecurity Schema Framework (OCSF) schema
+Author-email: Rick Mouritzen <rick@rickmode.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/ocsf/ocsf-schema-compiler
+Project-URL: Repository, https://github.com/ocsf/ocsf-schema-compiler.git
+Project-URL: Issues, https://github.com/ocsf/ocsf-schema-compiler/issues
+Keywords: compiler,ocsf,ocsf-schema,schema
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Software Development :: Compilers
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.14
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: bumpver; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Dynamic: license-file
+
+# OCSF Schema Compiler
+This is a Python library and command-line tool for compiling the Open Cybersecurity Schema Framework (OCSF) schema, specifically the schema at https://github.com/ocsf/ocsf-schema.
+
+## Getting started
+There are three ways to use the OCSF Schema Compiler:
+1. As a command-line tool, installed from PyPI.
+2. As a library, installed from PyPI.
+3. As a developer working on this project.
+
+Python version 3.14 or later is required.
+
+## Using `ocsf-schema-compiler` as a command-line tool
+Create a virtual environment then install with `pip`. For example:
+```shell
+python3 -m venv .venv
+source ./.venv/bin/activate
+python -m pip install ocsf-schema-compiler
+```
+
+Running from this environment is now a matter of calling `ocsf-schema-compiler`:
+```shell
+ocsf-schema-compiler -h
+```
+
+The basic usage is passing the base directory of a schema to the compiler and capturing the output to a file.
+```shell
+ocsf-schema-compiler path/to/ocsf-schema > schema.json
+```
+
+## Using `ocsf-schema-compiler` as a library
+Create a virtual environment then install with `pip`. For example:
+```shell
+python3 -m venv .venv
+source ./.venv/bin/activate
+pip install ocsf-schema-compiler
+```
+
+The compiler is implemented in the `SchemaCompiler` class. The class constructor the same options as the command-line tool. The class's `compile` method does the heavy lifting, returning a `dict` containing the compiled schema. More specifically, `compiler` returns an `ocsf_schema_compiler.jsonish.JObject`, which is a type alias for JSON-compatible `dict`.
+```python
+from pathlib import Path
+
+from ocsf_schema_compiler.compiler import SchemaCompiler
+
+
+compiler = SchemaCompiler(Path("path/to/ocsf-schema"))
+output = compiler.compile()
+```
+
+See `ocsf_schema_compiler.__main__` for a working example.
+
+## Developing `ocsf-schema-compiler`
+The recommended way to work on OCSF projects is via a fork into your own GitHub profile or organization. Create your fork of [this repo](https://github.com/ocsf/ocsf-schema-compiler) with the [GitHub CLI](https://cli.github.com/) tool (or, more painfully, manually).
+
+This project requires Python 3.14 or later, and otherwise has no runtime dependencies. This mean you can run it directly from a cloned repo's `src` directory without creating a virtual environment.
+
+I usually run with a subshell so my current directory remains in the base of the cloned repo. I also often use the [jq](https://jqlang.org/) tool to format the JSON output. For example:
+```shell
+cd path/to/ocsf-schema-compiler
+$(cd src && python3 -m ocsf_schema_compiler ~/path/to/ocsf-schema > jq -S > ~/path/to/output/schema.json)
+```
+
+This project has regression tests in the `tests` directory built using the `unittest` library. These also can be run without a virtual environment. The tests can be run with the `Makefile` target `tests`.
+```shell
+make tests
+```
+
+This project uses [Ruff](https://docs.astral.sh/ruff/) for linting and code formatting. Ruff's formatting is very similar to Black with some minor differences (improvements, in my opinion). This requires a virtual environment with both installed. With the virtual environment activated the linting and formatting can be run with the `Makefile` target `lint`.
+
+This project's `.gitignore` assumes the virtual environment is at `.venv`.
+
+```shell
+# A standard Python virtual environment works fine
+python3 -m venv .venv
+source ./.venv/bin/activate
+
+# Install the tools
+pip install ruff
+
+# Now the lint target will work
+make lint
+```
+
+Also with a virtual environment, a local install can be used to run the compiler.
+```shell
+# A standard Python virtual environment works fine
+python3 -m venv .venv
+source ./.venv/bin/activate
+
+pip install -e .
+```
+
+
+Integrating Ruff with your editor is recommended. See [Editor integration | Ruff](https://docs.astral.sh/ruff/editors/).
+
+## Publishing
+This project follows the publishing approach described by this tutorial: [How to Publish an Open-Source Python Package to PyPI — Real Python](https://realpython.com/pypi-publish-python-package/), including use of the [Build](https://pypa-build.readthedocs.io/) and [Twine](https://twine.readthedocs.io/) tools. The [BumpVer](https://pypi.org/project/bumpver/) tool is also used to increment versions and keep the various mentions of the version in sync.
+
+## Copyright
+Copyright © OCSF a Series of LF Projects, LLC. See [NOTICE](https://github.com/ocsf/ocsf-schema-compiler/blob/main/NOTICE) for details.
+
+## License
+This project is distributed under the Apache License Version 2.0. See [LICENSE](https://github.com/ocsf/ocsf-schema-compiler/blob/main/LICENSE) for details.

ocsf_schema_compiler-0.9.2/README.md

@@ -0,0 +1,102 @@
+# OCSF Schema Compiler
+This is a Python library and command-line tool for compiling the Open Cybersecurity Schema Framework (OCSF) schema, specifically the schema at https://github.com/ocsf/ocsf-schema.
+
+## Getting started
+There are three ways to use the OCSF Schema Compiler:
+1. As a command-line tool, installed from PyPI.
+2. As a library, installed from PyPI.
+3. As a developer working on this project.
+
+Python version 3.14 or later is required.
+
+## Using `ocsf-schema-compiler` as a command-line tool
+Create a virtual environment then install with `pip`. For example:
+```shell
+python3 -m venv .venv
+source ./.venv/bin/activate
+python -m pip install ocsf-schema-compiler
+```
+
+Running from this environment is now a matter of calling `ocsf-schema-compiler`:
+```shell
+ocsf-schema-compiler -h
+```
+
+The basic usage is passing the base directory of a schema to the compiler and capturing the output to a file.
+```shell
+ocsf-schema-compiler path/to/ocsf-schema > schema.json
+```
+
+## Using `ocsf-schema-compiler` as a library
+Create a virtual environment then install with `pip`. For example:
+```shell
+python3 -m venv .venv
+source ./.venv/bin/activate
+pip install ocsf-schema-compiler
+```
+
+The compiler is implemented in the `SchemaCompiler` class. The class constructor the same options as the command-line tool. The class's `compile` method does the heavy lifting, returning a `dict` containing the compiled schema. More specifically, `compiler` returns an `ocsf_schema_compiler.jsonish.JObject`, which is a type alias for JSON-compatible `dict`.
+```python
+from pathlib import Path
+
+from ocsf_schema_compiler.compiler import SchemaCompiler
+
+
+compiler = SchemaCompiler(Path("path/to/ocsf-schema"))
+output = compiler.compile()
+```
+
+See `ocsf_schema_compiler.__main__` for a working example.
+
+## Developing `ocsf-schema-compiler`
+The recommended way to work on OCSF projects is via a fork into your own GitHub profile or organization. Create your fork of [this repo](https://github.com/ocsf/ocsf-schema-compiler) with the [GitHub CLI](https://cli.github.com/) tool (or, more painfully, manually).
+
+This project requires Python 3.14 or later, and otherwise has no runtime dependencies. This mean you can run it directly from a cloned repo's `src` directory without creating a virtual environment.
+
+I usually run with a subshell so my current directory remains in the base of the cloned repo. I also often use the [jq](https://jqlang.org/) tool to format the JSON output. For example:
+```shell
+cd path/to/ocsf-schema-compiler
+$(cd src && python3 -m ocsf_schema_compiler ~/path/to/ocsf-schema > jq -S > ~/path/to/output/schema.json)
+```
+
+This project has regression tests in the `tests` directory built using the `unittest` library. These also can be run without a virtual environment. The tests can be run with the `Makefile` target `tests`.
+```shell
+make tests
+```
+
+This project uses [Ruff](https://docs.astral.sh/ruff/) for linting and code formatting. Ruff's formatting is very similar to Black with some minor differences (improvements, in my opinion). This requires a virtual environment with both installed. With the virtual environment activated the linting and formatting can be run with the `Makefile` target `lint`.
+
+This project's `.gitignore` assumes the virtual environment is at `.venv`.
+
+```shell
+# A standard Python virtual environment works fine
+python3 -m venv .venv
+source ./.venv/bin/activate
+
+# Install the tools
+pip install ruff
+
+# Now the lint target will work
+make lint
+```
+
+Also with a virtual environment, a local install can be used to run the compiler.
+```shell
+# A standard Python virtual environment works fine
+python3 -m venv .venv
+source ./.venv/bin/activate
+
+pip install -e .
+```
+
+
+Integrating Ruff with your editor is recommended. See [Editor integration | Ruff](https://docs.astral.sh/ruff/editors/).
+
+## Publishing
+This project follows the publishing approach described by this tutorial: [How to Publish an Open-Source Python Package to PyPI — Real Python](https://realpython.com/pypi-publish-python-package/), including use of the [Build](https://pypa-build.readthedocs.io/) and [Twine](https://twine.readthedocs.io/) tools. The [BumpVer](https://pypi.org/project/bumpver/) tool is also used to increment versions and keep the various mentions of the version in sync.
+
+## Copyright
+Copyright © OCSF a Series of LF Projects, LLC. See [NOTICE](https://github.com/ocsf/ocsf-schema-compiler/blob/main/NOTICE) for details.
+
+## License
+This project is distributed under the Apache License Version 2.0. See [LICENSE](https://github.com/ocsf/ocsf-schema-compiler/blob/main/LICENSE) for details.

ocsf_schema_compiler-0.9.2/pyproject.toml

@@ -0,0 +1,64 @@
+[build-system]
+requires = ["setuptools"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ocsf-schema-compiler"
+version = "0.9.2"
+description = "Compile an Open Cybersecurity Schema Framework (OCSF) schema"
+readme = "README.md"
+authors = [{ name = "Rick Mouritzen", email = "rick@rickmode.com" }]
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+keywords = ["compiler", "ocsf", "ocsf-schema", "schema"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Software Development :: Build Tools",
+    "Topic :: Software Development :: Compilers",
+    "Topic :: Software Development :: Libraries",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+]
+requires-python = ">= 3.14"
+
+[project.urls]
+Homepage = "https://github.com/ocsf/ocsf-schema-compiler"
+Repository = "https://github.com/ocsf/ocsf-schema-compiler.git"
+Issues = "https://github.com/ocsf/ocsf-schema-compiler/issues"
+
+[project.scripts]
+ocsf-schema-compiler = "ocsf_schema_compiler.__main__:main"
+
+[project.optional-dependencies]
+dev = ["bumpver", "ruff"]
+
+[tool.bumpver]
+current_version = "0.9.2"
+version_pattern = "MAJOR.MINOR.PATCH"
+commit_message = "Bump version {old_version} -> {new_version}"
+tag_message = "{new_version}"
+tag_scope = "default"
+pre_commit_hook = ""
+post_commit_hook = ""
+commit = true
+tag = true
+push = false
+
+[tool.bumpver.file_patterns]
+"pyproject.toml" = ['current_version = "{version}"', 'version = "{version}"']
+"src/ocsf_schema_compiler/__init__.py" = ["{version}"]
+
+[tool.ruff.lint]
+# E501 includes long strings in line-length checks.
+#      https://docs.astral.sh/ruff/rules/line-too-long/
+# W505 includes long comments in line-length checks when enabled by setting below
+#      https://docs.astral.sh/ruff/rules/doc-line-too-long/     
+extend-select = ["E501", "W505"]
+
+[tool.ruff.lint.pycodestyle]
+# max-doc-length = 88
+ignore-overlong-task-comments = false

ocsf_schema_compiler-0.9.2/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

ocsf_schema_compiler-0.9.2/src/ocsf_schema_compiler/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.9.2"

ocsf_schema_compiler-0.9.2/src/ocsf_schema_compiler/__main__.py

@@ -0,0 +1,113 @@
+import json
+import logging
+from argparse import ArgumentParser
+from pathlib import Path
+from sys import stderr
+from time import perf_counter
+
+from ocsf_schema_compiler import __version__
+from ocsf_schema_compiler.compiler import SchemaCompiler
+
+logger = logging.getLogger(__name__)
+
+
+def main():
+    parser = ArgumentParser(
+        description=f"Open Cybersecurity Schema Framework Schema Compiler, version "
+        f"{__version__}. Compile an OCSF schema directory structure down to a single"
+        " JSON object written to standard output. Logs are written to standard error."
+        " Source code at https://github.com/ocsf/ocsf-schema-compiler.",
+    )
+    parser.add_argument(
+        "path",
+        type=Path,
+        help="path to an OCSF schema directory (e.g., a git clone of"
+        " https://github.com/ocsf/ocsf-schema)",
+    )
+    parser.add_argument(
+        "-i",
+        "--ignore-platform-extensions",
+        action="store_true",
+        default=False,
+        help="ignore platform extensions (if any); these are in an extensions directory"
+        " under the schema directory; default: %(default)s",
+    )
+    parser.add_argument(
+        "-e",
+        "--extensions-path",
+        action="append",
+        type=Path,
+        metavar="PATH",
+        dest="extensions_paths",
+        help="optional path to a directory containing one or more OCSF schema"
+        " extensions; can be repeated",
+    )
+    group = parser.add_mutually_exclusive_group()
+    group.add_argument(
+        "-b",
+        "--browser-mode",
+        action="store_true",
+        default=False,
+        help="include extra information needed by the schema browser (the OCSF Server);"
+        " cannot be used with the -l, --legacy-mode option; default: %(default)s",
+    )
+    group.add_argument(
+        "-l",
+        "--legacy-mode",
+        action="store_true",
+        default=False,
+        help="output schema in legacy export schema layout; cannot be used with the"
+        " -b, --browser-mode option; default: %(default)s",
+    )
+    parser.add_argument(
+        "-s",
+        "--scope-extension-keys",
+        action="store_true",
+        default=False,
+        help="scope extension keys; can only be used with the -l, --legacy-mode option;"
+        " default: %(default)s",
+    )
+    parser.add_argument(
+        "--log-level",
+        choices=("DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"),
+        default="INFO",
+        help="set log level; logs are written to standard error; default: %(default)s",
+    )
+    parser.add_argument(
+        "-v",
+        "--version",
+        action="version",
+        version="%(prog)s " + __version__,
+    )
+
+    args = parser.parse_args()
+    if args.scope_extension_keys and not args.legacy_mode:
+        parser.error("-s, --scope-extension-keys requires -l, --legacy-mode")
+
+    logging.basicConfig(
+        format="%(levelname)s: %(message)s",
+        style="%",
+        stream=stderr,
+        level=args.log_level,
+    )
+
+    start_seconds = perf_counter()
+
+    compiler = SchemaCompiler(
+        args.path,
+        args.ignore_platform_extensions,
+        args.extensions_paths,
+        args.browser_mode,
+        args.legacy_mode,
+        args.scope_extension_keys,
+    )
+    output = compiler.compile()
+
+    duration = perf_counter() - start_seconds
+    logger.info("Schema compilation took %.3f seconds", duration)
+
+    print(json.dumps(output))
+
+
+if __name__ == "__main__":
+    main()