# PDS Lasso Reports
The PDS Lasso Reports package provides utilities to generates various kinds of reports. It provides four commands:
- `git-ping` which "pings" a branch by making an empty commit+push to it
- `summaries` which generates build summary tables in various formats
- `pds-plan` which creates planning board reports
- `pds-sloc` which analyzes and visualizes source lines of code (SLOC) across GitHub repositories
Please visit our website at: https://nasa-pds.github.io/lasso-reports
It may have useful information for developers and end-users.
## Prerequisites
Installing this software requires:
- `git` to be present on the target system
- `cloc` for SLOC analysis (install via your system's package manager, e.g. Homebrew)
- A GitHub personal access token (for accessing private repositories)
## User Quickstart
Install with:
pip install lasso-reports
### PDS SLOC
To execute pds-sloc, run:
# Basic usage - analyze NASA-PDS organization
pds-sloc --update --visualize
# Analyze a specific repository
pds-sloc --update --visualize --repo validate
# Initialize historical data from a specific date
pds-sloc --init-history 2023-01-01
# Generate visualizations from existing data
pds-sloc --visualize
# Use a specific GitHub token
pds-sloc --update --token YOUR_GITHUB_TOKEN
# Analyze a different organization
pds-sloc --update --visualize --org OTHER-ORG
The tool will generate:
- A CSV report with SLOC counts by repository and language
- Visualizations showing:
- Total SLOC by repository
- Language distribution
- Historical SLOC trends
- Most active repositories
For more options, run:
pds-sloc --help
## Code of Conduct
All users and developers of the NASA-PDS software are expected to abide by our [Code of Conduct](https://github.com/NASA-PDS/.github/blob/main/CODE_OF_CONDUCT.md). Please read this to ensure you understand the expectations of our community.
## Development
To develop this project, use your favorite text editor, or an integrated development environment with Python support, such as [PyCharm](https://www.jetbrains.com/pycharm/).
### Contributing
For information on how to contribute to NASA-PDS codebases please take a look at our [Contributing guidelines](https://github.com/NASA-PDS/.github/blob/main/CONTRIBUTING.md).
### Installation
Install in editable mode and with extra developer dependencies into your virtual environment of choice:
pip install --editable '.[dev]'
Configure the `pre-commit` hooks:
pre-commit install
pre-commit install -t pre-push
pre-commit install -t prepare-commit-msg
pre-commit install -t commit-msg
These hooks check code formatting and also aborts commits that contain secrets such as passwords or API keys. However, a one time setup is required in your global Git configuration. See [the wiki entry on Git Secrets](https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Git-and-Github-Guide#git-secrets) to learn how.
### Packaging
To isolate and be able to re-produce the environment for this package, you should use a [Python Virtual Environment](https://docs.python.org/3/tutorial/venv.html). To do so, run:
python3 -m venv venv
Then exclusively use `venv/bin/python`, `venv/bin/pip`, etc. Or, "activate" the virtual environment by sourcing the appropriate script in the `venv/bin` directory.
If you have `tox` installed and would like it to create your environment and install dependencies for you run:
tox --devenv <name you'd like for env> -e dev
Dependencies for development are specified as the `dev` `extras_require` in `setup.cfg`; they are installed into the virtual environment as follows:
pip install --editable '.[dev]'
All the source code is in a sub-directory under `src`.
### Tooling
The `dev` `extras_require` included in the template repo installs `black`, `flake8` (plus some plugins), and `mypy` along with default configuration for all of them. You can run all of these (and more!) with:
tox -e lint
Raw data
{
"_id": null,
"home_page": "https://github.com/NASA-PDS/lasso-reports",
"name": "lasso.reports",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.13",
"maintainer_email": null,
"keywords": "pds, planetary data, ci, automation, reports, reporting",
"author": "PDS",
"author_email": "pds_operator@jpl.nasa.gov",
"download_url": "https://github.com/NASA-PDS/lasso-reports/releases/",
"platform": null,
"description": "# PDS Lasso Reports\n\nThe PDS Lasso Reports package provides utilities to generates various kinds of reports. It provides four commands:\n\n- `git-ping` which \"pings\" a branch by making an empty commit+push to it\n- `summaries` which generates build summary tables in various formats\n- `pds-plan` which creates planning board reports\n- `pds-sloc` which analyzes and visualizes source lines of code (SLOC) across GitHub repositories\n\nPlease visit our website at: https://nasa-pds.github.io/lasso-reports\n\nIt may have useful information for developers and end-users.\n\n\n## Prerequisites\n\nInstalling this software requires:\n- `git` to be present on the target system\n- `cloc` for SLOC analysis (install via your system's package manager, e.g. Homebrew)\n- A GitHub personal access token (for accessing private repositories)\n\n\n## User Quickstart\n\nInstall with:\n\n pip install lasso-reports\n\n\n### PDS SLOC\n\nTo execute pds-sloc, run:\n\n # Basic usage - analyze NASA-PDS organization\n pds-sloc --update --visualize\n\n # Analyze a specific repository\n pds-sloc --update --visualize --repo validate\n\n # Initialize historical data from a specific date\n pds-sloc --init-history 2023-01-01\n\n # Generate visualizations from existing data\n pds-sloc --visualize\n\n # Use a specific GitHub token\n pds-sloc --update --token YOUR_GITHUB_TOKEN\n\n # Analyze a different organization\n pds-sloc --update --visualize --org OTHER-ORG\n\nThe tool will generate:\n- A CSV report with SLOC counts by repository and language\n- Visualizations showing:\n - Total SLOC by repository\n - Language distribution\n - Historical SLOC trends\n - Most active repositories\n\nFor more options, run:\n pds-sloc --help\n\n\n## Code of Conduct\n\nAll users and developers of the NASA-PDS software are expected to abide by our [Code of Conduct](https://github.com/NASA-PDS/.github/blob/main/CODE_OF_CONDUCT.md). Please read this to ensure you understand the expectations of our community.\n\n\n## Development\n\nTo develop this project, use your favorite text editor, or an integrated development environment with Python support, such as [PyCharm](https://www.jetbrains.com/pycharm/).\n\n\n### Contributing\n\nFor information on how to contribute to NASA-PDS codebases please take a look at our [Contributing guidelines](https://github.com/NASA-PDS/.github/blob/main/CONTRIBUTING.md).\n\n\n### Installation\n\nInstall in editable mode and with extra developer dependencies into your virtual environment of choice:\n\n pip install --editable '.[dev]'\n\nConfigure the `pre-commit` hooks:\n\n pre-commit install\n pre-commit install -t pre-push\n pre-commit install -t prepare-commit-msg\n pre-commit install -t commit-msg\n\nThese hooks check code formatting and also aborts commits that contain secrets such as passwords or API keys. However, a one time setup is required in your global Git configuration. See [the wiki entry on Git Secrets](https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Git-and-Github-Guide#git-secrets) to learn how.\n\n\n### Packaging\n\nTo isolate and be able to re-produce the environment for this package, you should use a [Python Virtual Environment](https://docs.python.org/3/tutorial/venv.html). To do so, run:\n\n python3 -m venv venv\n\nThen exclusively use `venv/bin/python`, `venv/bin/pip`, etc. Or, \"activate\" the virtual environment by sourcing the appropriate script in the `venv/bin` directory.\n\nIf you have `tox` installed and would like it to create your environment and install dependencies for you run:\n\n tox --devenv <name you'd like for env> -e dev\n\nDependencies for development are specified as the `dev` `extras_require` in `setup.cfg`; they are installed into the virtual environment as follows:\n\n pip install --editable '.[dev]'\n\nAll the source code is in a sub-directory under `src`.\n\n\n### Tooling\n\nThe `dev` `extras_require` included in the template repo installs `black`, `flake8` (plus some plugins), and `mypy` along with default configuration for all of them. You can run all of these (and more!) with:\n\n tox -e lint\n",
"bugtrack_url": null,
"license": "apache-2.0",
"summary": "Reporting support for the Planetary Data System",
"version": "1.1.0",
"project_urls": {
"Download": "https://github.com/NASA-PDS/lasso-reports/releases/",
"Homepage": "https://github.com/NASA-PDS/lasso-reports"
},
"split_keywords": [
"pds",
" planetary data",
" ci",
" automation",
" reports",
" reporting"
],
"urls": [
{
"comment_text": "\ud83e\udd20 Yee-haw! This here ar-tee-fact got done uploaded by the Roundup!",
"digests": {
"blake2b_256": "4fbc79bde75cb7da2b98caee4b195b0d1088a9873a17ac3a0e637348f7199375",
"md5": "8b1e72149eb8c5cbe2732f2f4fd5d8b5",
"sha256": "83ce308453c11482c3787d4107742e1d9a3c2fd62243184c37c0c12d90f92320"
},
"downloads": -1,
"filename": "lasso_reports-1.1.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "8b1e72149eb8c5cbe2732f2f4fd5d8b5",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.13",
"size": 85802,
"upload_time": "2025-09-03T14:47:38",
"upload_time_iso_8601": "2025-09-03T14:47:38.274967Z",
"url": "https://files.pythonhosted.org/packages/4f/bc/79bde75cb7da2b98caee4b195b0d1088a9873a17ac3a0e637348f7199375/lasso_reports-1.1.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-09-03 14:47:38",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "NASA-PDS",
"github_project": "lasso-reports",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "lasso.reports"
}
JSON
