|Build_Status| |Coverage| |Version| |Documentation_Status|
====================
`cti-stix-validator`
====================
NOTE: This is an `OASIS TC Open Repository <https://www.oasis-
open.org/resources/open-repositories/>`__. See the `Governance`_
section for more information.
The STIX Validator checks that STIX JSON content conforms to the
requirements specified in the STIX 2.1 specification. In addition to
checking conformance with the `JSON schemas <https://github.com/oasis-
open/cti-stix2-json-schemas>`_, the validator checks conformance with
requirements that cannot be specified in JSON schema, as well as with
established "best practices". This validator is non-normative; in
cases of conflict with the STIX 2.1 specification, the specification
takes precedence.
The STIX 2.1 specification contains two types of requirements:
mandatory "MUST" requirements, and recommended "SHOULD" best practice
requirements. The validator checks documents against the "MUST"
requirements using JSON schemas. Some of these mandatory requirements
cannot be implemented in JSON Schema, however, so the validator uses
Python functions to check them. The "SHOULD" requirements are all
checked by Python functions, and options may be used to ignore some or
all of these recommended "best practices."
The only exception to this is the mandatory requirement that an
object's 'type' be one of those defined by a STIX Object in the
specification. This rules out custom objects, so this check was made
optional.
The validator also color-codes its output to make it easier to tell at
a glance whether validation passed.
`Installation`
==============
The easiest way to install the STIX validator is with pip:
::
$ pip install stix2-validator
`Usage`
=======
As A Script
-----------
The validator comes with a bundled script which you can use to
validate a JSON file containing STIX content:
::
$ stix2_validator <stix_file.json>
As A Library
------------
You can also use this library to integrate STIX validation into your
own tools. You can validate a JSON file:
.. code:: python
from stix2validator import validate_file, print_results
results = validate_file("stix_file.json")
print_results(results)
You can also validate a JSON string using ``validate_string()``, or a Python
dictionary representing a STIX object using ``validate_instance()``. For more
information, see the full documentation
`here <https://stix2-validator.readthedocs.io/en/latest/usage.html>`_.
Governance
==========
This GitHub public repository ( `https://github.com/oasis-open/cti-
stix-validator <https://github.com/oasis-open/cti-stix-validator>`_ )
was `proposed <https://lists.oasis-
open.org/archives/cti/201609/msg00001.html>`_ and `approved
<https://www.oasis-open.org/committees/ballot.php?id=2971>`_ [`bis
<https://issues.oasis-open.org/browse/TCADMIN-2434>`_] by the `OASIS
Cyber Threat Intelligence (CTI) TC <https://www.oasis-
open.org/committees/cti/>`_ as an `OASIS TC Open Repository
<https://www.oasis-open.org/resources/open-repositories/>`__ to support
development of open source resources related to Technical Committee
work.
While this TC Open Repository remains associated with the sponsor TC,
its development priorities, leadership, intellectual property terms,
participation rules, and other matters of governance are `separate and
distinct <https://github.com/oasis-open/cti-stix-
validator/blob/master/CONTRIBUTING.md#governance-distinct-from-oasis-
tc-process>`_ from the OASIS TC Process and related policies.
All contributions made to this TC Open Repository are subject to open
source license terms expressed in the `BSD-3-Clause License
<https://www.oasis-open.org/sites/www.oasis-open.org/files/BSD-3-
Clause.txt>`_. That license was selected as the declared `"Applicable
License" <https://www.oasis-open.org/resources/open-
repositories/licenses>`_ when the TC Open Repository was created.
As documented in `"Public Participation Invited"
<https://github.com/oasis-open/cti-stix-
validator/blob/master/CONTRIBUTING.md#public-participation-invited>`_,
contributions to this OASIS TC Open Repository are invited from all
parties, whether affiliated with OASIS or not. Participants must have
a GitHub account, but no fees or OASIS membership obligations are
required. Participation is expected to be consistent with the `OASIS
TC Open Repository Guidelines and Procedures <https://www.oasis-
open.org/policies-guidelines/open-repositories>`_, the open source
`LICENSE <https://github.com/oasis-open/cti-stix-
validator/blob/master/LICENSE>`_ designated for this particular
repository, and the requirement for an `Individual Contributor License
Agreement <https://www.oasis-open.org/resources/open-
repositories/cla/individual-cla>`_ that governs intellectual property.
`Maintainers`
=============
TC Open Repository `Maintainers <https://www.oasis-
open.org/resources/open-repositories/maintainers-guide>`__ are
responsible for oversight of this project's community development
activities, including evaluation of GitHub `pull requests
<https://github.com/oasis-open/cti-stix-
validator/blob/master/CONTRIBUTING.md#fork-and-pull-collaboration-
model>`_ and `preserving <https://www.oasis-open.org/policies-
guidelines/open-repositories#repositoryManagement>`_ open source
principles of openness and fairness. Maintainers are recognized and
trusted experts who serve to implement community goals and consensus
design preferences.
Initially, the associated TC members have designated one or more
persons to serve as Maintainer(s); subsequently, participating
community members may select additional or substitute Maintainers, per
`consensus agreements <https://www.oasis-open.org/resources/open-
repositories/maintainers-guide#additionalMaintainers>`_.
.. _currentMaintainers:
**Current Maintainers of this TC Open Repository**
.. Initial Maintainers: Greg Back & Ivan Kirillov & Chris Lenk
* `Emily Ratliff <mailto:emily.ratliff@ibm.com>`__; GitHub ID: `https://github.com/ejratl <https://github.com/ejratl>`_; WWW: `IBM <http://www.ibm.com/>`__
* `Duncan Sparrell <mailto:duncan@sfractal.com>`__; GitHub ID: `https://github.com/sparrell <https://github.com/sparrell>`_; WWW: `sFractal <http://sfractal.com/>`__
* `Jason Keirstead <mailto:Jason.Keirstead@ca.ibm.com>`__; GitHub ID: `https://github.com/JasonKeirstead <https://github.com/JasonKeirstead>`_; WWW: `IBM <http://www.ibm.com/>`__
.. _aboutOpenRepos:
`About OASIS TC Open Repositories`
==================================
* `TC Open Repositories: Overview and Resources <https://www.oasis-open.org/resources/open-repositories/>`_
* `Frequently Asked Questions <https://www.oasis-open.org/resources/open-repositories/faq>`_
* `Open Source Licenses <https://www.oasis-open.org/resources/open-repositories/licenses>`_
* `Contributor License Agreements (CLAs) <https://www.oasis-open.org/resources/open-repositories/cla>`_
* `Maintainers' Guidelines and Agreement <https://www.oasis-open.org/resources/open-repositories/maintainers-guide>`__
`Feedback`
==========
Questions or comments about this TC Open Repository's activities
should be composed as GitHub issues or comments. If use of an
issue/comment is not possible or appropriate, questions may be
directed by email to the Maintainer(s) `listed above
<#currentmaintainers>`_. Please send general questions about TC Open
Repository participation to OASIS Staff at `repository-admin@oasis-
open.org <mailto:repository-admin@oasis-open.org>`_ and any specific
CLA-related questions to `repository-cla@oasis-open.org
<mailto:repository-cla@oasis-open.org>`_.
.. |Build_Status| image:: https://github.com/oasis-open/cti-stix-validator/workflows/cti-stix-validator%20test%20harness/badge.svg
:target: https://github.com/oasis-open/cti-stix-validator/actions?query=workflow%3A%22cti-stix-validator+test+harness%22
.. |Coverage| image:: https://codecov.io/gh/oasis-open/cti-stix-validator/branch/master/graph/badge.svg
:target: https://codecov.io/gh/oasis-open/cti-stix-validator
.. |Version| image:: https://img.shields.io/pypi/v/stix2-validator.svg?maxAge=3600
:target: https://pypi.python.org/pypi/stix2-validator/
.. |Documentation_Status| image:: https://readthedocs.org/projects/stix2-validator/badge/?version=latest
:target: https://stix2-validator.readthedocs.io/en/latest/
:alt: Documentation Status
Raw data
{
"_id": null,
"home_page": "https://github.com/oasis-open/cti-stix-validator",
"name": "stix2-validator",
"maintainer": "Chris Lenk",
"docs_url": null,
"requires_python": "",
"maintainer_email": "clenk@mitre.org",
"keywords": "stix stix2 json validation validator stix-validator stix2-validator",
"author": "OASIS Cyber Threat Intelligence Technical Committee",
"author_email": "cti-users@lists.oasis-open.org",
"download_url": "https://files.pythonhosted.org/packages/37/df/c601368f033773a35d692d3299019818d95e501bd605974310bd5424ebdc/stix2-validator-3.1.4.tar.gz",
"platform": null,
"description": "|Build_Status| |Coverage| |Version| |Documentation_Status|\n\n====================\n`cti-stix-validator`\n====================\nNOTE: This is an `OASIS TC Open Repository <https://www.oasis-\nopen.org/resources/open-repositories/>`__. See the `Governance`_\nsection for more information.\n\nThe STIX Validator checks that STIX JSON content conforms to the\nrequirements specified in the STIX 2.1 specification. In addition to\nchecking conformance with the `JSON schemas <https://github.com/oasis-\nopen/cti-stix2-json-schemas>`_, the validator checks conformance with\nrequirements that cannot be specified in JSON schema, as well as with\nestablished \"best practices\". This validator is non-normative; in\ncases of conflict with the STIX 2.1 specification, the specification\ntakes precedence.\n\nThe STIX 2.1 specification contains two types of requirements:\nmandatory \"MUST\" requirements, and recommended \"SHOULD\" best practice\nrequirements. The validator checks documents against the \"MUST\"\nrequirements using JSON schemas. Some of these mandatory requirements\ncannot be implemented in JSON Schema, however, so the validator uses\nPython functions to check them. The \"SHOULD\" requirements are all\nchecked by Python functions, and options may be used to ignore some or\nall of these recommended \"best practices.\"\n\nThe only exception to this is the mandatory requirement that an\nobject's 'type' be one of those defined by a STIX Object in the\nspecification. This rules out custom objects, so this check was made\noptional.\n\nThe validator also color-codes its output to make it easier to tell at\na glance whether validation passed.\n\n`Installation`\n==============\n\nThe easiest way to install the STIX validator is with pip:\n\n::\n\n $ pip install stix2-validator\n\n`Usage`\n=======\n\nAs A Script\n-----------\n\nThe validator comes with a bundled script which you can use to\nvalidate a JSON file containing STIX content:\n\n::\n\n $ stix2_validator <stix_file.json>\n\nAs A Library\n------------\n\nYou can also use this library to integrate STIX validation into your\nown tools. You can validate a JSON file:\n\n.. code:: python\n\n from stix2validator import validate_file, print_results\n\n results = validate_file(\"stix_file.json\")\n print_results(results)\n\nYou can also validate a JSON string using ``validate_string()``, or a Python\ndictionary representing a STIX object using ``validate_instance()``. For more\ninformation, see the full documentation\n`here <https://stix2-validator.readthedocs.io/en/latest/usage.html>`_.\n\nGovernance\n==========\n\nThis GitHub public repository ( `https://github.com/oasis-open/cti-\nstix-validator <https://github.com/oasis-open/cti-stix-validator>`_ )\nwas `proposed <https://lists.oasis-\nopen.org/archives/cti/201609/msg00001.html>`_ and `approved\n<https://www.oasis-open.org/committees/ballot.php?id=2971>`_ [`bis\n<https://issues.oasis-open.org/browse/TCADMIN-2434>`_] by the `OASIS\nCyber Threat Intelligence (CTI) TC <https://www.oasis-\nopen.org/committees/cti/>`_ as an `OASIS TC Open Repository\n<https://www.oasis-open.org/resources/open-repositories/>`__ to support\ndevelopment of open source resources related to Technical Committee\nwork.\n\nWhile this TC Open Repository remains associated with the sponsor TC,\nits development priorities, leadership, intellectual property terms,\nparticipation rules, and other matters of governance are `separate and\ndistinct <https://github.com/oasis-open/cti-stix-\nvalidator/blob/master/CONTRIBUTING.md#governance-distinct-from-oasis-\ntc-process>`_ from the OASIS TC Process and related policies.\n\nAll contributions made to this TC Open Repository are subject to open\nsource license terms expressed in the `BSD-3-Clause License\n<https://www.oasis-open.org/sites/www.oasis-open.org/files/BSD-3-\nClause.txt>`_. That license was selected as the declared `\"Applicable\nLicense\" <https://www.oasis-open.org/resources/open-\nrepositories/licenses>`_ when the TC Open Repository was created.\n\nAs documented in `\"Public Participation Invited\"\n<https://github.com/oasis-open/cti-stix-\nvalidator/blob/master/CONTRIBUTING.md#public-participation-invited>`_,\ncontributions to this OASIS TC Open Repository are invited from all\nparties, whether affiliated with OASIS or not. Participants must have\na GitHub account, but no fees or OASIS membership obligations are\nrequired. Participation is expected to be consistent with the `OASIS\nTC Open Repository Guidelines and Procedures <https://www.oasis-\nopen.org/policies-guidelines/open-repositories>`_, the open source\n`LICENSE <https://github.com/oasis-open/cti-stix-\nvalidator/blob/master/LICENSE>`_ designated for this particular\nrepository, and the requirement for an `Individual Contributor License\nAgreement <https://www.oasis-open.org/resources/open-\nrepositories/cla/individual-cla>`_ that governs intellectual property.\n\n`Maintainers`\n=============\nTC Open Repository `Maintainers <https://www.oasis-\nopen.org/resources/open-repositories/maintainers-guide>`__ are\nresponsible for oversight of this project's community development\nactivities, including evaluation of GitHub `pull requests\n<https://github.com/oasis-open/cti-stix-\nvalidator/blob/master/CONTRIBUTING.md#fork-and-pull-collaboration-\nmodel>`_ and `preserving <https://www.oasis-open.org/policies-\nguidelines/open-repositories#repositoryManagement>`_ open source\nprinciples of openness and fairness. Maintainers are recognized and\ntrusted experts who serve to implement community goals and consensus\ndesign preferences.\n\nInitially, the associated TC members have designated one or more\npersons to serve as Maintainer(s); subsequently, participating\ncommunity members may select additional or substitute Maintainers, per\n`consensus agreements <https://www.oasis-open.org/resources/open-\nrepositories/maintainers-guide#additionalMaintainers>`_.\n\n.. _currentMaintainers:\n\n**Current Maintainers of this TC Open Repository**\n\n.. Initial Maintainers: Greg Back & Ivan Kirillov & Chris Lenk\n\n* `Emily Ratliff <mailto:emily.ratliff@ibm.com>`__; GitHub ID: `https://github.com/ejratl <https://github.com/ejratl>`_; WWW: `IBM <http://www.ibm.com/>`__\n* `Duncan Sparrell <mailto:duncan@sfractal.com>`__; GitHub ID: `https://github.com/sparrell <https://github.com/sparrell>`_; WWW: `sFractal <http://sfractal.com/>`__\n* `Jason Keirstead <mailto:Jason.Keirstead@ca.ibm.com>`__; GitHub ID: `https://github.com/JasonKeirstead <https://github.com/JasonKeirstead>`_; WWW: `IBM <http://www.ibm.com/>`__\n\n.. _aboutOpenRepos:\n\n`About OASIS TC Open Repositories`\n==================================\n* `TC Open Repositories: Overview and Resources <https://www.oasis-open.org/resources/open-repositories/>`_\n* `Frequently Asked Questions <https://www.oasis-open.org/resources/open-repositories/faq>`_\n* `Open Source Licenses <https://www.oasis-open.org/resources/open-repositories/licenses>`_\n* `Contributor License Agreements (CLAs) <https://www.oasis-open.org/resources/open-repositories/cla>`_\n* `Maintainers' Guidelines and Agreement <https://www.oasis-open.org/resources/open-repositories/maintainers-guide>`__\n\n`Feedback`\n==========\nQuestions or comments about this TC Open Repository's activities\nshould be composed as GitHub issues or comments. If use of an\nissue/comment is not possible or appropriate, questions may be\ndirected by email to the Maintainer(s) `listed above\n<#currentmaintainers>`_. Please send general questions about TC Open\nRepository participation to OASIS Staff at `repository-admin@oasis-\nopen.org <mailto:repository-admin@oasis-open.org>`_ and any specific\nCLA-related questions to `repository-cla@oasis-open.org\n<mailto:repository-cla@oasis-open.org>`_.\n\n\n\n.. |Build_Status| image:: https://github.com/oasis-open/cti-stix-validator/workflows/cti-stix-validator%20test%20harness/badge.svg\n :target: https://github.com/oasis-open/cti-stix-validator/actions?query=workflow%3A%22cti-stix-validator+test+harness%22\n.. |Coverage| image:: https://codecov.io/gh/oasis-open/cti-stix-validator/branch/master/graph/badge.svg\n :target: https://codecov.io/gh/oasis-open/cti-stix-validator\n.. |Version| image:: https://img.shields.io/pypi/v/stix2-validator.svg?maxAge=3600\n :target: https://pypi.python.org/pypi/stix2-validator/\n.. |Documentation_Status| image:: https://readthedocs.org/projects/stix2-validator/badge/?version=latest\n :target: https://stix2-validator.readthedocs.io/en/latest/\n :alt: Documentation Status\n\n\n\n",
"bugtrack_url": null,
"license": "",
"summary": "APIs and scripts for validating STIX 2.x documents.",
"version": "3.1.4",
"project_urls": {
"Bug Tracker": "https://github.com/oasis-open/cti-stix-validator/issues/",
"Documentation": "https://stix2-validator.readthedocs.io/",
"Homepage": "https://github.com/oasis-open/cti-stix-validator",
"Source Code": "https://github.com/oasis-open/cti-stix-validator/"
},
"split_keywords": [
"stix",
"stix2",
"json",
"validation",
"validator",
"stix-validator",
"stix2-validator"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a001c3db25e4fba8a9fa60a99c19bd9c77023d12ec135764f8f9899b98a1a61c",
"md5": "2f3d8d4070ce92ac2755731be3aa5eb2",
"sha256": "4b8870de4c5da8f26266c0997628dd9e18d31d6fa42c24b4a54f1de6fb4eccac"
},
"downloads": -1,
"filename": "stix2_validator-3.1.4-py2.py3-none-any.whl",
"has_sig": false,
"md5_digest": "2f3d8d4070ce92ac2755731be3aa5eb2",
"packagetype": "bdist_wheel",
"python_version": "py2.py3",
"requires_python": null,
"size": 259792,
"upload_time": "2023-07-25T22:08:06",
"upload_time_iso_8601": "2023-07-25T22:08:06.486065Z",
"url": "https://files.pythonhosted.org/packages/a0/01/c3db25e4fba8a9fa60a99c19bd9c77023d12ec135764f8f9899b98a1a61c/stix2_validator-3.1.4-py2.py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "37dfc601368f033773a35d692d3299019818d95e501bd605974310bd5424ebdc",
"md5": "b37f0130002caf5db26037556d140cd8",
"sha256": "0977c8608041ba4defa8d054b0e3e9955cf33d60bed5bc6735bcec1af147960c"
},
"downloads": -1,
"filename": "stix2-validator-3.1.4.tar.gz",
"has_sig": false,
"md5_digest": "b37f0130002caf5db26037556d140cd8",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 183373,
"upload_time": "2023-07-25T22:08:08",
"upload_time_iso_8601": "2023-07-25T22:08:08.721176Z",
"url": "https://files.pythonhosted.org/packages/37/df/c601368f033773a35d692d3299019818d95e501bd605974310bd5424ebdc/stix2-validator-3.1.4.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-07-25 22:08:08",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "oasis-open",
"github_project": "cti-stix-validator",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"tox": true,
"lcname": "stix2-validator"
}
JSON
