| Name | spdx-tools JSON |
| Version |
0.8.2
JSON |
| download |
| home_page | |
| Summary | SPDX parser and tools. |
| upload_time | 2023-10-12 12:28:43 |
| maintainer | SPDX group at the Linux Foundation and others |
| docs_url | None |
| author | |
| requires_python | >=3.7 |
| license | Apache-2.0 |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# Python library to parse, validate and create SPDX documents
CI status (Linux, macOS and Windows): [![Install and Test][1]][2]
[1]: https://github.com/spdx/tools-python/actions/workflows/install_and_test.yml/badge.svg
[2]: https://github.com/spdx/tools-python/actions/workflows/install_and_test.yml
# Breaking changes v0.7 -> v0.8
Please be aware that the upcoming 0.8 release has undergone a significant refactoring in preparation for the upcoming
SPDX v3.0 release, leading to breaking changes in the API.
Please refer to the [migration guide](https://github.com/spdx/tools-python/wiki/How-to-migrate-from-0.7-to-0.8)
to update your existing code.
The main features of v0.8 are:
- full validation of SPDX documents against the v2.2 and v2.3 specification
- support for SPDX's RDF format with all v2.3 features
- experimental support for the upcoming SPDX v3 specification. Note, however, that support is neither complete nor
stable at this point, as the spec is still evolving. SPDX3-related code is contained in a separate subpackage "spdx3"
and its use is optional. We do not recommend using it in production code yet.
# Information
This library implements SPDX parsers, convertors, validators and handlers in Python.
- Home: https://github.com/spdx/tools-python
- Issues: https://github.com/spdx/tools-python/issues
- PyPI: https://pypi.python.org/pypi/spdx-tools
- Browse the API: https://spdx.github.io/tools-python
Important updates regarding this library are shared via the SPDX tech mailing list: https://lists.spdx.org/g/Spdx-tech.
# License
[Apache-2.0](LICENSE)
# Features
* API to create and manipulate SPDX v2.2 and v2.3 documents
* Parse, convert, create and validate SPDX files
* supported formats: Tag/Value, RDF, JSON, YAML, XML
* visualize the structure of a SPDX document by creating an `AGraph`. Note: This is an optional feature and requires
additional installation of optional dependencies
## Experimental support for SPDX 3.0
* Create v3.0 elements and payloads
* Convert v2.2/v2.3 documents to v3.0
* Serialize to JSON-LD
See [Quickstart to SPDX 3.0](#quickstart-to-spdx-30) below.
The implementation is based on the descriptive markdown files in the repository https://github.com/spdx/spdx-3-model (latest commit: a5372a3c145dbdfc1381fc1f791c68889aafc7ff).
# Installation
As always you should work in a virtualenv (venv). You can install a local clone
of this repo with `yourenv/bin/pip install .` or install it from PyPI
(check for the [newest release](https://pypi.org/project/spdx-tools/#history) and install it like
`yourenv/bin/pip install spdx-tools==0.8.0a2`). Note that on Windows it would be `Scripts`
instead of `bin`.
# How to use
## Command-line usage
1. **PARSING/VALIDATING** (for parsing any format):
* Use `pyspdxtools -i <filename>` where `<filename>` is the location of the file. The input format is inferred automatically from the file ending.
* If you are using a source distribution, try running:
`pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json`
2. **CONVERTING** (for converting one format to another):
* Use `pyspdxtools -i <input_file> -o <output_file>` where `<input_file>` is the location of the file to be converted
and `<output_file>` is the location of the output file. The input and output formats are inferred automatically from the file endings.
* If you are using a source distribution, try running:
`pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json -o output.tag`
* If you want to skip the validation process, provide the `--novalidation` flag, like so:
`pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json -o output.tag --novalidation`
(use this with caution: note that undetected invalid documents may lead to unexpected behavior of the tool)
* For help use `pyspdxtools --help`
3. **GRAPH GENERATION** (optional feature)
* This feature generates a graph representing all elements in the SPDX document and their connections based on the provided
relationships. The graph can be rendered to a picture. Below is an example for the file `tests/data/SPDXJSONExample-v2.3.spdx.json`:
* Make sure you install the optional dependencies `networkx` and `pygraphviz`. To do so run `pip install ".[graph_generation]"`.
* Use `pyspdxtools -i <input_file> --graph -o <output_file>` where `<output_file>` is an output file name with valid format for `pygraphviz` (check
the documentation [here](https://pygraphviz.github.io/documentation/stable/reference/agraph.html#pygraphviz.AGraph.draw)).
* If you are using a source distribution, try running
`pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json --graph -o SPDXJSONExample-v2.3.spdx.png` to generate
a png with an overview of the structure of the example file.
## Library usage
1. **DATA MODEL**
* The `spdx_tools.spdx.model` package constitutes the internal SPDX v2.3 data model (v2.2 is simply a subset of this). All relevant classes for SPDX document creation are exposed in the `__init__.py` found [here](src%2Fspdx_tools%2Fspdx%2Fmodel%2F__init__.py).
* SPDX objects are implemented via `@dataclass_with_properties`, a custom extension of `@dataclass`.
* Each class starts with a list of its properties and their possible types. When no default value is provided, the property is mandatory and must be set during initialization.
* Using the type hints, type checking is enforced when initializing a new instance or setting/getting a property on an instance
(wrong types will raise `ConstructorTypeError` or `TypeError`, respectively). This makes it easy to catch invalid properties early and only construct valid documents.
* Note: in-place manipulations like `list.append(item)` will circumvent the type checking (a `TypeError` will still be raised when reading `list` again). We recommend using `list = list + [item]` instead.
* The main entry point of an SPDX document is the `Document` class from the [document.py](src%2Fspdx_tools%2Fspdx%2Fmodel%2Fdocument.py) module, which links to all other classes.
* For license handling, the [license_expression](https://github.com/nexB/license-expression) library is used.
* Note on `documentDescribes` and `hasFiles`: These fields will be converted to relationships in the internal data model. As they are deprecated, these fields will not be written in the output.
2. **PARSING**
* Use `parse_file(file_name)` from the `parse_anything.py` module to parse an arbitrary file with one of the supported file endings.
* Successful parsing will return a `Document` instance. Unsuccessful parsing will raise `SPDXParsingError` with a list of all encountered problems.
3. **VALIDATING**
* Use `validate_full_spdx_document(document)` to validate an instance of the `Document` class.
* This will return a list of `ValidationMessage` objects, each consisting of a String describing the invalidity and a `ValidationContext` to pinpoint the source of the validation error.
* Validation depends on the SPDX version of the document. Note that only versions `SPDX-2.2` and `SPDX-2.3` are supported by this tool.
4. **WRITING**
* Use `write_file(document, file_name)` from the `write_anything.py` module to write a `Document` instance to the specified file.
The serialization format is determined from the filename ending.
* Validation is performed per default prior to the writing process, which is cancelled if the document is invalid. You can skip the validation via `write_file(document, file_name, validate=False)`.
Caution: Only valid documents can be serialized reliably; serialization of invalid documents is not supported.
## Example
Here are some examples of possible use cases to quickly get you started with the spdx-tools.
If you want more examples, like how to create an SPDX document from scratch, have a look [at the examples folder](examples).
```python
import logging
from license_expression import get_spdx_licensing
from spdx_tools.spdx.model import (Checksum, ChecksumAlgorithm, File,
FileType, Relationship, RelationshipType)
from spdx_tools.spdx.parser.parse_anything import parse_file
from spdx_tools.spdx.validation.document_validator import validate_full_spdx_document
from spdx_tools.spdx.writer.write_anything import write_file
# read in an SPDX document from a file
document = parse_file("spdx_document.json")
# change the document's name
document.creation_info.name = "new document name"
# define a file and a DESCRIBES relationship between the file and the document
checksum = Checksum(ChecksumAlgorithm.SHA1, "71c4025dd9897b364f3ebbb42c484ff43d00791c")
file = File(name="./fileName.py", spdx_id="SPDXRef-File", checksums=[checksum],
file_types=[FileType.TEXT],
license_concluded=get_spdx_licensing().parse("MIT and GPL-2.0"),
license_comment="licenseComment", copyright_text="copyrightText")
relationship = Relationship("SPDXRef-DOCUMENT", RelationshipType.DESCRIBES, "SPDXRef-File")
# add the file and the relationship to the document
# (note that we do not use "document.files.append(file)" as that would circumvent the type checking)
document.files = document.files + [file]
document.relationships = document.relationships + [relationship]
# validate the edited document and log the validation messages
# (depending on your use case, you might also want to utilize the validation_message.context)
validation_messages = validate_full_spdx_document(document)
for validation_message in validation_messages:
logging.warning(validation_message.validation_message)
# if there are no validation messages, the document is valid
# and we can safely serialize it without validating again
if not validation_messages:
write_file(document, "new_spdx_document.rdf", validate=False)
```
# Quickstart to SPDX 3.0
In contrast to SPDX v2, all elements are now subclasses of the central `Element` class.
This includes packages, files, snippets, relationships, annotations, but also SBOMs, SpdxDocuments, and more.
For serialization purposes, all Elements that are to be serialized into the same file are collected in a `Payload`.
This is just a dictionary that maps each Element's SpdxId to itself.
Use the `write_payload()` functions to serialize a payload.
There currently are two options:
* The `spdx_tools.spdx3.writer.json_ld.json_ld_writer` module generates a JSON-LD file of the payload.
* The `spdx_tools.spdx3.writer.console.payload_writer` module prints a debug output to console. Note that this is not an official part of the SPDX specification and will probably be dropped as soon as a better standard emerges.
You can convert an SPDX v2 document to v3 via the `spdx_tools.spdx3.bump_from_spdx2.spdx_document` module.
The `bump_spdx_document()` function will return a payload containing an `SpdxDocument` Element and one Element for each package, file, snippet, relationship, or annotation contained in the v2 document.
# Dependencies
* PyYAML: https://pypi.org/project/PyYAML/ for handling YAML.
* xmltodict: https://pypi.org/project/xmltodict/ for handling XML.
* rdflib: https://pypi.python.org/pypi/rdflib/ for handling RDF.
* ply: https://pypi.org/project/ply/ for handling tag-value.
* click: https://pypi.org/project/click/ for creating the CLI interface.
* beartype: https://pypi.org/project/beartype/ for type checking.
* uritools: https://pypi.org/project/uritools/ for validation of URIs.
* license-expression: https://pypi.org/project/license-expression/ for handling SPDX license expressions.
# Support
* Submit issues, questions or feedback at https://github.com/spdx/tools-python/issues
* Join the chat at https://gitter.im/spdx-org/Lobby
* Join the discussion on https://lists.spdx.org/g/spdx-tech and
https://spdx.dev/participate/tech/
# Contributing
Contributions are very welcome! See [CONTRIBUTING.md](./CONTRIBUTING.md) for instructions on how to contribute to the
codebase.
# History
This is the result of an initial GSoC contribution by @[ah450](https://github.com/ah450)
(or https://github.com/a-h-i) and is maintained by a community of SPDX adopters and enthusiasts.
In order to prepare for the release of SPDX v3.0, the repository has undergone a major refactoring during the time from 11/2022 to 07/2023.
Raw data
{
"_id": null,
"home_page": "",
"name": "spdx-tools",
"maintainer": "SPDX group at the Linux Foundation and others",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "Philippe Ombredanne <pombredanne@gmail.com>",
"keywords": "",
"author": "",
"author_email": "\"Ahmed H. Ismail\" <ahm3d.hisham@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/32/d8/a67445be5981469fdbaf7f765f53c920f699e7e512cc931b650a935c3199/spdx-tools-0.8.2.tar.gz",
"platform": null,
"description": "# Python library to parse, validate and create SPDX documents\n\nCI status (Linux, macOS and Windows): [![Install and Test][1]][2]\n\n[1]: https://github.com/spdx/tools-python/actions/workflows/install_and_test.yml/badge.svg\n\n[2]: https://github.com/spdx/tools-python/actions/workflows/install_and_test.yml\n\n\n# Breaking changes v0.7 -> v0.8\n\nPlease be aware that the upcoming 0.8 release has undergone a significant refactoring in preparation for the upcoming\nSPDX v3.0 release, leading to breaking changes in the API.\nPlease refer to the [migration guide](https://github.com/spdx/tools-python/wiki/How-to-migrate-from-0.7-to-0.8)\nto update your existing code.\n\nThe main features of v0.8 are:\n- full validation of SPDX documents against the v2.2 and v2.3 specification\n- support for SPDX's RDF format with all v2.3 features\n- experimental support for the upcoming SPDX v3 specification. Note, however, that support is neither complete nor \n stable at this point, as the spec is still evolving. SPDX3-related code is contained in a separate subpackage \"spdx3\" \n and its use is optional. We do not recommend using it in production code yet.\n\n\n# Information\n\nThis library implements SPDX parsers, convertors, validators and handlers in Python.\n\n- Home: https://github.com/spdx/tools-python\n- Issues: https://github.com/spdx/tools-python/issues\n- PyPI: https://pypi.python.org/pypi/spdx-tools\n- Browse the API: https://spdx.github.io/tools-python\n\nImportant updates regarding this library are shared via the SPDX tech mailing list: https://lists.spdx.org/g/Spdx-tech.\n\n\n# License\n\n[Apache-2.0](LICENSE)\n\n# Features\n\n* API to create and manipulate SPDX v2.2 and v2.3 documents\n* Parse, convert, create and validate SPDX files\n* supported formats: Tag/Value, RDF, JSON, YAML, XML\n* visualize the structure of a SPDX document by creating an `AGraph`. Note: This is an optional feature and requires \nadditional installation of optional dependencies\n\n## Experimental support for SPDX 3.0\n* Create v3.0 elements and payloads\n* Convert v2.2/v2.3 documents to v3.0\n* Serialize to JSON-LD\n\nSee [Quickstart to SPDX 3.0](#quickstart-to-spdx-30) below. \nThe implementation is based on the descriptive markdown files in the repository https://github.com/spdx/spdx-3-model (latest commit: a5372a3c145dbdfc1381fc1f791c68889aafc7ff).\n\n\n# Installation\n\nAs always you should work in a virtualenv (venv). You can install a local clone\nof this repo with `yourenv/bin/pip install .` or install it from PyPI \n(check for the [newest release](https://pypi.org/project/spdx-tools/#history) and install it like\n`yourenv/bin/pip install spdx-tools==0.8.0a2`). Note that on Windows it would be `Scripts`\ninstead of `bin`.\n\n# How to use\n\n## Command-line usage\n\n1. **PARSING/VALIDATING** (for parsing any format):\n\n* Use `pyspdxtools -i <filename>` where `<filename>` is the location of the file. The input format is inferred automatically from the file ending.\n\n* If you are using a source distribution, try running: \n `pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json`\n\n2. **CONVERTING** (for converting one format to another):\n\n* Use `pyspdxtools -i <input_file> -o <output_file>` where `<input_file>` is the location of the file to be converted\n and `<output_file>` is the location of the output file. The input and output formats are inferred automatically from the file endings.\n\n* If you are using a source distribution, try running: \n `pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json -o output.tag` \n\n* If you want to skip the validation process, provide the `--novalidation` flag, like so: \n `pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json -o output.tag --novalidation` \n (use this with caution: note that undetected invalid documents may lead to unexpected behavior of the tool)\n \n* For help use `pyspdxtools --help`\n\n3. **GRAPH GENERATION** (optional feature)\n\n* This feature generates a graph representing all elements in the SPDX document and their connections based on the provided\n relationships. The graph can be rendered to a picture. Below is an example for the file `tests/data/SPDXJSONExample-v2.3.spdx.json`:\n\n* Make sure you install the optional dependencies `networkx` and `pygraphviz`. To do so run `pip install \".[graph_generation]\"`.\n* Use `pyspdxtools -i <input_file> --graph -o <output_file>` where `<output_file>` is an output file name with valid format for `pygraphviz` (check \n the documentation [here](https://pygraphviz.github.io/documentation/stable/reference/agraph.html#pygraphviz.AGraph.draw)). \n* If you are using a source distribution, try running\n `pyspdxtools -i tests/data/SPDXJSONExample-v2.3.spdx.json --graph -o SPDXJSONExample-v2.3.spdx.png` to generate \n a png with an overview of the structure of the example file. \n\n## Library usage\n1. **DATA MODEL**\n * The `spdx_tools.spdx.model` package constitutes the internal SPDX v2.3 data model (v2.2 is simply a subset of this). All relevant classes for SPDX document creation are exposed in the `__init__.py` found [here](src%2Fspdx_tools%2Fspdx%2Fmodel%2F__init__.py).\n * SPDX objects are implemented via `@dataclass_with_properties`, a custom extension of `@dataclass`.\n * Each class starts with a list of its properties and their possible types. When no default value is provided, the property is mandatory and must be set during initialization.\n * Using the type hints, type checking is enforced when initializing a new instance or setting/getting a property on an instance\n (wrong types will raise `ConstructorTypeError` or `TypeError`, respectively). This makes it easy to catch invalid properties early and only construct valid documents.\n * Note: in-place manipulations like `list.append(item)` will circumvent the type checking (a `TypeError` will still be raised when reading `list` again). We recommend using `list = list + [item]` instead.\n * The main entry point of an SPDX document is the `Document` class from the [document.py](src%2Fspdx_tools%2Fspdx%2Fmodel%2Fdocument.py) module, which links to all other classes.\n * For license handling, the [license_expression](https://github.com/nexB/license-expression) library is used.\n * Note on `documentDescribes` and `hasFiles`: These fields will be converted to relationships in the internal data model. As they are deprecated, these fields will not be written in the output.\n2. **PARSING**\n * Use `parse_file(file_name)` from the `parse_anything.py` module to parse an arbitrary file with one of the supported file endings.\n * Successful parsing will return a `Document` instance. Unsuccessful parsing will raise `SPDXParsingError` with a list of all encountered problems.\n3. **VALIDATING**\n * Use `validate_full_spdx_document(document)` to validate an instance of the `Document` class.\n * This will return a list of `ValidationMessage` objects, each consisting of a String describing the invalidity and a `ValidationContext` to pinpoint the source of the validation error.\n * Validation depends on the SPDX version of the document. Note that only versions `SPDX-2.2` and `SPDX-2.3` are supported by this tool.\n4. **WRITING**\n * Use `write_file(document, file_name)` from the `write_anything.py` module to write a `Document` instance to the specified file.\n The serialization format is determined from the filename ending.\n * Validation is performed per default prior to the writing process, which is cancelled if the document is invalid. You can skip the validation via `write_file(document, file_name, validate=False)`.\n Caution: Only valid documents can be serialized reliably; serialization of invalid documents is not supported.\n\n## Example\nHere are some examples of possible use cases to quickly get you started with the spdx-tools.\nIf you want more examples, like how to create an SPDX document from scratch, have a look [at the examples folder](examples).\n```python\nimport logging\n\nfrom license_expression import get_spdx_licensing\n\nfrom spdx_tools.spdx.model import (Checksum, ChecksumAlgorithm, File, \n FileType, Relationship, RelationshipType)\nfrom spdx_tools.spdx.parser.parse_anything import parse_file\nfrom spdx_tools.spdx.validation.document_validator import validate_full_spdx_document\nfrom spdx_tools.spdx.writer.write_anything import write_file\n\n# read in an SPDX document from a file\ndocument = parse_file(\"spdx_document.json\")\n\n# change the document's name\ndocument.creation_info.name = \"new document name\"\n\n# define a file and a DESCRIBES relationship between the file and the document\nchecksum = Checksum(ChecksumAlgorithm.SHA1, \"71c4025dd9897b364f3ebbb42c484ff43d00791c\")\n\nfile = File(name=\"./fileName.py\", spdx_id=\"SPDXRef-File\", checksums=[checksum], \n file_types=[FileType.TEXT], \n license_concluded=get_spdx_licensing().parse(\"MIT and GPL-2.0\"),\n license_comment=\"licenseComment\", copyright_text=\"copyrightText\")\n\nrelationship = Relationship(\"SPDXRef-DOCUMENT\", RelationshipType.DESCRIBES, \"SPDXRef-File\")\n\n# add the file and the relationship to the document \n# (note that we do not use \"document.files.append(file)\" as that would circumvent the type checking)\ndocument.files = document.files + [file]\ndocument.relationships = document.relationships + [relationship]\n\n# validate the edited document and log the validation messages\n# (depending on your use case, you might also want to utilize the validation_message.context)\nvalidation_messages = validate_full_spdx_document(document)\nfor validation_message in validation_messages:\n logging.warning(validation_message.validation_message)\n\n# if there are no validation messages, the document is valid \n# and we can safely serialize it without validating again\nif not validation_messages:\n write_file(document, \"new_spdx_document.rdf\", validate=False)\n```\n\n# Quickstart to SPDX 3.0\nIn contrast to SPDX v2, all elements are now subclasses of the central `Element` class.\nThis includes packages, files, snippets, relationships, annotations, but also SBOMs, SpdxDocuments, and more. \nFor serialization purposes, all Elements that are to be serialized into the same file are collected in a `Payload`.\nThis is just a dictionary that maps each Element's SpdxId to itself.\nUse the `write_payload()` functions to serialize a payload.\nThere currently are two options: \n* The `spdx_tools.spdx3.writer.json_ld.json_ld_writer` module generates a JSON-LD file of the payload.\n* The `spdx_tools.spdx3.writer.console.payload_writer` module prints a debug output to console. Note that this is not an official part of the SPDX specification and will probably be dropped as soon as a better standard emerges.\n\nYou can convert an SPDX v2 document to v3 via the `spdx_tools.spdx3.bump_from_spdx2.spdx_document` module.\nThe `bump_spdx_document()` function will return a payload containing an `SpdxDocument` Element and one Element for each package, file, snippet, relationship, or annotation contained in the v2 document.\n\n\n# Dependencies\n\n* PyYAML: https://pypi.org/project/PyYAML/ for handling YAML.\n* xmltodict: https://pypi.org/project/xmltodict/ for handling XML.\n* rdflib: https://pypi.python.org/pypi/rdflib/ for handling RDF.\n* ply: https://pypi.org/project/ply/ for handling tag-value.\n* click: https://pypi.org/project/click/ for creating the CLI interface.\n* beartype: https://pypi.org/project/beartype/ for type checking.\n* uritools: https://pypi.org/project/uritools/ for validation of URIs.\n* license-expression: https://pypi.org/project/license-expression/ for handling SPDX license expressions.\n\n# Support\n\n* Submit issues, questions or feedback at https://github.com/spdx/tools-python/issues\n* Join the chat at https://gitter.im/spdx-org/Lobby\n* Join the discussion on https://lists.spdx.org/g/spdx-tech and\n https://spdx.dev/participate/tech/\n\n# Contributing\n\nContributions are very welcome! See [CONTRIBUTING.md](./CONTRIBUTING.md) for instructions on how to contribute to the\ncodebase.\n\n# History\n\nThis is the result of an initial GSoC contribution by @[ah450](https://github.com/ah450)\n(or https://github.com/a-h-i) and is maintained by a community of SPDX adopters and enthusiasts.\nIn order to prepare for the release of SPDX v3.0, the repository has undergone a major refactoring during the time from 11/2022 to 07/2023.\n",
"bugtrack_url": null,
"license": "Apache-2.0",
"summary": "SPDX parser and tools.",
"version": "0.8.2",
"project_urls": {
"Homepage": "https://github.com/spdx/tools-python"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a2a35d311af9214f65b0e7106f13d14b677563533f81b4953578023051f4f916",
"md5": "3c17de3e1235c19b84dc6dea4e73c968",
"sha256": "8c336c873f9caaf110693a1d38c007031e67bea53aa4b881007b680be66de934"
},
"downloads": -1,
"filename": "spdx_tools-0.8.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "3c17de3e1235c19b84dc6dea4e73c968",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 285129,
"upload_time": "2023-10-12T12:28:41",
"upload_time_iso_8601": "2023-10-12T12:28:41.074598Z",
"url": "https://files.pythonhosted.org/packages/a2/a3/5d311af9214f65b0e7106f13d14b677563533f81b4953578023051f4f916/spdx_tools-0.8.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "32d8a67445be5981469fdbaf7f765f53c920f699e7e512cc931b650a935c3199",
"md5": "39f69c958c47c210bb9651bcf5cb9cb7",
"sha256": "aea4ac9c2c375e7f439b1cef5ff32ef34914c083de0f61e08ed67cd3d9deb2a9"
},
"downloads": -1,
"filename": "spdx-tools-0.8.2.tar.gz",
"has_sig": false,
"md5_digest": "39f69c958c47c210bb9651bcf5cb9cb7",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 680032,
"upload_time": "2023-10-12T12:28:43",
"upload_time_iso_8601": "2023-10-12T12:28:43.551685Z",
"url": "https://files.pythonhosted.org/packages/32/d8/a67445be5981469fdbaf7f765f53c920f699e7e512cc931b650a935c3199/spdx-tools-0.8.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-10-12 12:28:43",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "spdx",
"github_project": "tools-python",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"appveyor": true,
"lcname": "spdx-tools"
}
