Software Systems Laboratory Metrics GitHub Issue Spoilage
A
pythontool to calculate the issue spoilage of a GitHub repository
Table of Contents
About
The Software Systems Laboratory (SSL) GitHub Issue Spoilage Project is a python tool to calculate the issue spoilage of a GitHub repository. It is reliant upon the output of the GitHub Issue tool.
This project is licensed under the BSD-3-Clause. See the LICENSE for more information.
Developer Tooling
To maximize the utility of this project and the greater SSL Metrics project, the following software packages are required:
Operating System
All tools developed for the greater SSL Metrics project must target Mac OS and Linux. SSL Metrics software is not supported or recommended to run on Windows but can be modified to do so at your own risk.
It is recomendded to develop on Mac OS or Linux. However, if you are on a Windows machine, you can use WSL to develop as well.
How To Use
Installation
You can install the tool via pip with either of the two following one-liners:
pip install --upgrade pip ssl-metrics-metapip install --upgrade pip ssl-metrics-github-issue-spoilage
Command Line Arguements
ssl-metrics-github-issue-spoilage-graph -h
options:
-h, --help show this help message and exit
-u UPPER_WINDOW_BOUND, --upper-window-bound UPPER_WINDOW_BOUND
Argument to specify the max number of days to look at. NOTE: window bounds are inclusive.
-l LOWER_WINDOW_BOUND, --lower-window-bound LOWER_WINDOW_BOUND
Argument to specify the start of the window of time to analyze. NOTE: window bounds are inclusive.
-c CLOSED_ISSUES_GRAPH_FILENAME, --closed-issues-graph-filename CLOSED_ISSUES_GRAPH_FILENAME
The filename of the output graph of closed issues
-i INPUT, --input INPUT
The input JSON file that is to be used for graphing
-d LINE_OF_ISSUES_SPOILAGE_FILENAME, --line-of-issues-spoilage-filename LINE_OF_ISSUES_SPOILAGE_FILENAME
The filename of the output graph of spoiled issues
-o OPEN_ISSUES_GRAPH_FILENAME, --open-issues-graph-filename OPEN_ISSUES_GRAPH_FILENAME
The filename of the output graph of open issues
-x JOINT_GRAPH_FILENAME, --joint-graph-filename JOINT_GRAPH_FILENAME
The filename of the joint output graph of open and closed issues
Metadata
Release files for ssl-metrics-github-issue-spoilage 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ssl-metrics-github-issue-spoilage-0.2.tar.gz | 5.8 kB | Without provenance | Details for ssl-metrics-github-issue-spoilage-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ssl_metrics_github_issue_spoilage-0.2-py3-none-any.whl | Python 3 | none | any | Details for ssl_metrics_github_issue_spoilage-0.2-py3-none-any.whl |
Total release size: 12.9 kB
Release files / ssl-metrics-github-issue-spoilage-0.2.tar.gz
| Download URL | ssl-metrics-github-issue-spoilage-0.2.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c4f0df555c8320fcf7ee8cc98e75b0964f81ba80f1e94bc4bd967eba0abc36d
|
|
BLAKE2b-256 checksum How to use checksums |
c7a017586c63fdcec0c5ad4fbea6a0e12ff0fe462d2ecddf3a565dc809a15557
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Release files / ssl_metrics_github_issue_spoilage-0.2-py3-none-any.whl
| Download URL | ssl_metrics_github_issue_spoilage-0.2-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b1d8e9b190aa1a0de145491b4bbbc2cd2dff95ebd4afe85e3d435bd4250611a
|
|
BLAKE2b-256 checksum How to use checksums |
771109a43640fd94dee88dec5ee7e164816cf5b5baf846d8b1f069658da7f9bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Security for ssl-metrics-github-issue-spoilage 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.