Name | gitlabcis JSON |
Version |
1.4.1
JSON |
| download |
home_page | None |
Summary | An automated tool that assesses the GitLab CIS benchmarks against a project. |
upload_time | 2024-11-21 01:56:45 |
maintainer | None |
docs_url | None |
author | None |
requires_python | >=3.8 |
license | MIT License Copyright (c) 2024 GitLab Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
keywords |
gitlab benchmarks
cis benchmarks
gitlab hardening
gitlab recommendations
gitlabcis
gitlab cis benchmarks
gitlabcis
gitlab
cis
benchmark scanner
gitlab cis benchmark scanner
gitlab cis
|
VCS |
|
bugtrack_url |
|
requirements |
No requirements were recorded.
|
Travis-CI |
No Travis.
|
coveralls test coverage |
No coveralls.
|
# CIS GitLab Benchmark Scanner - gitlabcis
## Background
On April 17th 2024, [GitLab™](https://about.gitlab.com/) published [a blog post](https://about.gitlab.com/blog/2024/04/17/gitlab-introduces-new-cis-benchmark-for-improved-security/) introducing its Center for Internet Security® (CIS) GitLab Benchmark. With the goal to improve the security of the product and offer hardening recommendations to GitLab's customers. You can download a copy of the benchmarks which are published on the [Center for Internet Security® website](https://workbench.cisecurity.org/benchmarks/17538).
> _"The CIS GitLab Benchmark stemmed from a collaboration between CIS and GitLab's Field Security and Product Management teams. After numerous conversations with customers, we understood the need for a specific benchmark that would guide their hardening efforts. We conducted an in-depth review of GitLab’s product and documentation to understand how our offering mapped to CIS's Software Supply Chain Security Benchmark. After the initial draft was ready, it entered into the CIS consensus process, where the broader CIS Benchmark Community was able to review it and suggest edits prior to publication."_
>
> _Ref: [Creating the CIS GitLab Benchmark](https://about.gitlab.com/blog/2024/04/17/gitlab-introduces-new-cis-benchmark-for-improved-security/#creating-the-cis-gitlab-benchmark)_
## Overview
`gitlabcis` is a [Python®](https://www.python.org/downloads/) package which audits a GitLab project against the [Center for Internet Security® (CIS) GitLab Benchmark](https://workbench.cisecurity.org/benchmarks/17538). It includes [recommendations-as-code](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/tree/main/gitlabcis/recommendations?ref_type=heads#recommendations) formatted in [YAML™](https://yaml.org/).
## GitLab Product Enhancement
### Compliance Adherence Report
There is a larger effort to [add the CIS Benchmark](https://gitlab.com/groups/gitlab-org/-/epics/13823) as a compliance standard to the [Compliance Adherence Report](https://gitlab.com/groups/gitlab-org/-/epics/7854).
- Once implemented, this will enable customers to automatically have visibility into whether there are additional measures they need to take in order to comply with the measures recommended in the CIS Benchmark.
### Contributing back to GitLab
Through the course of developing this tool, the authors contributed 2 features to the GitLab product (#39):
- [Show Crosslinked/related issues in merge requests via the API](https://gitlab.com/gitlab-org/gitlab/-/issues/461536)
- [Groups API: Add Restrict group access by Domain](https://gitlab.com/gitlab-org/gitlab/-/issues/351494)
## Table of Contents
[[_TOC_]]
### Disclaimers
| Disclaimer | Comment |
| -----------| ------- |
| This tool assumes that one is using GitLab for [everything](https://about.gitlab.com/blog/2016/03/08/gitlab-tutorial-its-all-connected/) | <ul><li>For example, the first recommendation ([1.1.1 - version_control](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/gitlabcis/recommendations/source_code_1/code_changes_1_1/version_control.yml#L4)):</li><ul><li>_"Ensure any changes to code are tracked in a version control platform."_</ul><li>Using GitLab automatically passes this control.</li></ul> |
| This tool cannot audit every recommendation | <ul><li>We have kept a record of every recommendation that we cannot automate. Review our limitations doc ([docs/limitations.md](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/limitations.md?ref_type=heads)), which highlights automation gaps in which a condition cannot confidently be automated.</li></ul> |
| This tool **does not execute any write operations** on your GitLab project | <ul><li>This tool is expressly designed to refrain from performing any write operations that may:</li><ul><li>modify, alter, change, or otherwise impact the configuration, data, or integrity of your GitLab project</li></ul> <li>ensuring that no alterations or unauthorized adjustments are made to its state or contents.</li></ul> |
| This is not an official GitLab product | <ul><li>This repository was created by GitLab engineers and is not officially supported by GitLab.</li></ul> |
### Getting started
- **Required:**
- You need to have [python®](https://www.python.org/downloads/) & [pip](https://pip.pypa.io/en/stable/installation/) installed
- **One of:**
- GitLab [Personal Access Token (PAT)](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html)
- GitLab [OAuth Token](https://docs.gitlab.com/ee/security/tokens/#oauth-20-tokens)
#### Tokens
`gitlabcis` **requires** one of the following tokens:
##### Personal Access Token (PAT)
- Create a [Personal Access Token (PAT)](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token).
You can either pass the token as an option or store it as an environment variable:
- `GITLAB_TOKEN` - (_optional_) Environment Variable
- `--token` / `-t` - (_optional_) gitlabcis token option
##### OAuth Token
- Create an [OAuth Token](https://docs.gitlab.com/ee/api/oauth2.html).
You can either pass the token as an option or store it as an environment variable:
- `GITLAB_OAUTH_TOKEN` - (_optional_) Environment Variable
- `--oauth-token` / `-ot` - (_optional_) gitlabcis token option
##### Token Scope
- **Required:** Your token needs to have _at least_ the `read_api` scope.
- (_optional_) Providing your token more scope will unlock more controls that require higher levels of permission.
#### Install
There's a number of ways to download the scanner. Please see them below:
##### Pypi
Install `gitlabcis` from pypi.org:
```sh
pip install gitlabcis
```
##### GitLab
Install `gitlabcis` from the [package registry](https://gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/packages/):
```sh
pip install gitlabcis --index-url https://gitlab.com/api/v4/projects/57279821/packages/pypi/simple
```
If you haven't already done so, you will need to add the below to your `.pypirc` file.
```ini
[gitlab]
repository = https://gitlab.com/api/v4/projects/57279821/packages/pypi
username = __token__
password = <your personal access token>
```
Install `gitlabcis` from source via clone, or our [releases page](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/releases)
```sh
# make a clone (or create a local fork) of the repo
git clone git@gitlab.com:gitlab-org/govern/compliance/engineering/cis/gitlabcis.git
cd cis-benchmark-scanner
make install
```
#### Usage
The following syntax is expected:
```sh
gitlabcis URL OPTIONS
```
#### Screenshot
![results](docs/img/results.png)
#### Generate a report
To generate a report from the shell:
```sh
gitlabcis https://gitlab.example.com/path/to/project --token $TOKEN
```
Generate a json report: (_Using the `$GITLAB_TOKEN` variable, you do not need to specify `--token` option_)
```sh
gitlabcis \
https://gitlab.example.com/path/to/project \
-o results.json \
-f json
```
To execute a single control:
```sh
gitlabcis \
https://gitlab.example.com/path/to/project \
-ids 1.2.3 # or multiple: 2.3.4 3.4.5 etc
```
## Documentation
Review the `gitlabcis` [documentation (./docs)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/tree/main/docs?ref_type=heads) directory - _Something missing?_ Feel free to create contribute with a [new issue](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/issues/new).
## License
`gitlabcis` was published using the [MIT license](https://opensource.org/license/mit), it can be reviewed in the [./LICENSE](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/LICENSE?ref_type=heads) file.
## Changelog
See the [./CHANGELOG.md](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/CHANGELOG.md?ref_type=heads) for more information.
## Developers
### Code of Conduct
Review the heading section of [contributing doc (docs/CONTRIBUTING.md)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/CONTRIBUTING.md?ref_type=heads) for the code of conduct.
### Security
Review our [security policy (docs/SECURITY.md)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/SECURITY.md?ref_type=heads) document which outlines how to disclose a vulnerability.
### Contributing
Do you want to contribute? - Fantastic! Check out the [contributing doc (docs/CONTRIBUTING.md)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/CONTRIBUTING.md?ref_type=heads) for more information.
Raw data
{
"_id": null,
"home_page": null,
"name": "gitlabcis",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "GitLab Benchmarks, CIS Benchmarks, GitLab Hardening, GitLab Recommendations, GitLabcis, GitLab CIS Benchmarks, gitlabcis, GitLab, CIS, Benchmark Scanner, GitLab CIS Benchmark scanner, GitLab CIS",
"author": null,
"author_email": "Nate Rosandich <nrosandich+gitlabcis@gitlab.com>, Neil McDonald <nmcdonald+gitlabcis@gitlab.com>, Mitra JozeNazemian <mjozenazemian+gitlabcis@gitlab.com>",
"download_url": "https://files.pythonhosted.org/packages/bd/d6/4a6c246c0d3b34e2665774e3b0040f811ceb413da8f3cb1385123b1485af/gitlabcis-1.4.1.tar.gz",
"platform": null,
"description": "# CIS GitLab Benchmark Scanner - gitlabcis\n\n## Background\n\nOn April 17th 2024, [GitLab\u2122](https://about.gitlab.com/) published [a blog post](https://about.gitlab.com/blog/2024/04/17/gitlab-introduces-new-cis-benchmark-for-improved-security/) introducing its Center for Internet Security\u00ae (CIS) GitLab Benchmark. With the goal to improve the security of the product and offer hardening recommendations to GitLab's customers. You can download a copy of the benchmarks which are published on the [Center for Internet Security\u00ae website](https://workbench.cisecurity.org/benchmarks/17538).\n\n> _\"The CIS GitLab Benchmark stemmed from a collaboration between CIS and GitLab's Field Security and Product Management teams. After numerous conversations with customers, we understood the need for a specific benchmark that would guide their hardening efforts. We conducted an in-depth review of GitLab\u2019s product and documentation to understand how our offering mapped to CIS's Software Supply Chain Security Benchmark. After the initial draft was ready, it entered into the CIS consensus process, where the broader CIS Benchmark Community was able to review it and suggest edits prior to publication.\"_\n>\n> _Ref: [Creating the CIS GitLab Benchmark](https://about.gitlab.com/blog/2024/04/17/gitlab-introduces-new-cis-benchmark-for-improved-security/#creating-the-cis-gitlab-benchmark)_\n\n## Overview\n\n`gitlabcis` is a [Python\u00ae](https://www.python.org/downloads/) package which audits a GitLab project against the [Center for Internet Security\u00ae (CIS) GitLab Benchmark](https://workbench.cisecurity.org/benchmarks/17538). It includes [recommendations-as-code](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/tree/main/gitlabcis/recommendations?ref_type=heads#recommendations) formatted in [YAML\u2122](https://yaml.org/).\n\n## GitLab Product Enhancement\n\n### Compliance Adherence Report\n\nThere is a larger effort to [add the CIS Benchmark](https://gitlab.com/groups/gitlab-org/-/epics/13823) as a compliance standard to the [Compliance Adherence Report](https://gitlab.com/groups/gitlab-org/-/epics/7854).\n\n- Once implemented, this will enable customers to automatically have visibility into whether there are additional measures they need to take in order to comply with the measures recommended in the CIS Benchmark.\n\n### Contributing back to GitLab\n\nThrough the course of developing this tool, the authors contributed 2 features to the GitLab product (#39):\n\n- [Show Crosslinked/related issues in merge requests via the API](https://gitlab.com/gitlab-org/gitlab/-/issues/461536)\n- [Groups API: Add Restrict group access by Domain](https://gitlab.com/gitlab-org/gitlab/-/issues/351494)\n\n## Table of Contents\n\n[[_TOC_]]\n\n### Disclaimers\n\n| Disclaimer | Comment |\n| -----------| ------- |\n| This tool assumes that one is using GitLab for [everything](https://about.gitlab.com/blog/2016/03/08/gitlab-tutorial-its-all-connected/) | <ul><li>For example, the first recommendation ([1.1.1 - version_control](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/gitlabcis/recommendations/source_code_1/code_changes_1_1/version_control.yml#L4)):</li><ul><li>_\"Ensure any changes to code are tracked in a version control platform.\"_</ul><li>Using GitLab automatically passes this control.</li></ul> |\n| This tool cannot audit every recommendation | <ul><li>We have kept a record of every recommendation that we cannot automate. Review our limitations doc ([docs/limitations.md](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/limitations.md?ref_type=heads)), which highlights automation gaps in which a condition cannot confidently be automated.</li></ul> |\n| This tool **does not execute any write operations** on your GitLab project | <ul><li>This tool is expressly designed to refrain from performing any write operations that may:</li><ul><li>modify, alter, change, or otherwise impact the configuration, data, or integrity of your GitLab project</li></ul> <li>ensuring that no alterations or unauthorized adjustments are made to its state or contents.</li></ul> |\n| This is not an official GitLab product | <ul><li>This repository was created by GitLab engineers and is not officially supported by GitLab.</li></ul> |\n\n### Getting started\n\n- **Required:**\n - You need to have [python\u00ae](https://www.python.org/downloads/) & [pip](https://pip.pypa.io/en/stable/installation/) installed\n - **One of:**\n - GitLab [Personal Access Token (PAT)](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html)\n - GitLab [OAuth Token](https://docs.gitlab.com/ee/security/tokens/#oauth-20-tokens)\n\n#### Tokens\n\n`gitlabcis` **requires** one of the following tokens:\n\n##### Personal Access Token (PAT)\n\n- Create a [Personal Access Token (PAT)](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token).\n\nYou can either pass the token as an option or store it as an environment variable:\n\n- `GITLAB_TOKEN` - (_optional_) Environment Variable\n- `--token` / `-t` - (_optional_) gitlabcis token option\n\n##### OAuth Token\n\n- Create an [OAuth Token](https://docs.gitlab.com/ee/api/oauth2.html).\n\nYou can either pass the token as an option or store it as an environment variable:\n\n- `GITLAB_OAUTH_TOKEN` - (_optional_) Environment Variable\n- `--oauth-token` / `-ot` - (_optional_) gitlabcis token option\n\n##### Token Scope\n\n- **Required:** Your token needs to have _at least_ the `read_api` scope.\n- (_optional_) Providing your token more scope will unlock more controls that require higher levels of permission.\n\n#### Install\n\nThere's a number of ways to download the scanner. Please see them below:\n\n##### Pypi\n\nInstall `gitlabcis` from pypi.org:\n\n```sh\npip install gitlabcis\n```\n\n##### GitLab\n\nInstall `gitlabcis` from the [package registry](https://gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/packages/):\n\n```sh\npip install gitlabcis --index-url https://gitlab.com/api/v4/projects/57279821/packages/pypi/simple\n```\n\nIf you haven't already done so, you will need to add the below to your `.pypirc` file.\n\n```ini\n[gitlab]\nrepository = https://gitlab.com/api/v4/projects/57279821/packages/pypi\nusername = __token__\npassword = <your personal access token>\n```\n\nInstall `gitlabcis` from source via clone, or our [releases page](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/releases)\n\n```sh\n# make a clone (or create a local fork) of the repo\ngit clone git@gitlab.com:gitlab-org/govern/compliance/engineering/cis/gitlabcis.git\ncd cis-benchmark-scanner\nmake install\n```\n\n#### Usage\n\nThe following syntax is expected:\n\n```sh\ngitlabcis URL OPTIONS\n```\n\n#### Screenshot\n\n![results](docs/img/results.png)\n\n#### Generate a report\n\nTo generate a report from the shell:\n\n```sh\ngitlabcis https://gitlab.example.com/path/to/project --token $TOKEN\n```\n\nGenerate a json report: (_Using the `$GITLAB_TOKEN` variable, you do not need to specify `--token` option_)\n\n```sh\ngitlabcis \\\n https://gitlab.example.com/path/to/project \\\n -o results.json \\\n -f json\n```\n\nTo execute a single control:\n\n```sh\ngitlabcis \\\n https://gitlab.example.com/path/to/project \\\n -ids 1.2.3 # or multiple: 2.3.4 3.4.5 etc\n```\n\n## Documentation\n\nReview the `gitlabcis` [documentation (./docs)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/tree/main/docs?ref_type=heads) directory - _Something missing?_ Feel free to create contribute with a [new issue](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/issues/new).\n\n## License\n\n`gitlabcis` was published using the [MIT license](https://opensource.org/license/mit), it can be reviewed in the [./LICENSE](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/LICENSE?ref_type=heads) file.\n\n## Changelog\n\nSee the [./CHANGELOG.md](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/CHANGELOG.md?ref_type=heads) for more information.\n\n## Developers\n\n### Code of Conduct\n\nReview the heading section of [contributing doc (docs/CONTRIBUTING.md)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/CONTRIBUTING.md?ref_type=heads) for the code of conduct.\n\n### Security\n\nReview our [security policy (docs/SECURITY.md)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/SECURITY.md?ref_type=heads) document which outlines how to disclose a vulnerability.\n\n### Contributing\n\nDo you want to contribute? - Fantastic! Check out the [contributing doc (docs/CONTRIBUTING.md)](https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/blob/main/docs/CONTRIBUTING.md?ref_type=heads) for more information.\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2024 GitLab Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "An automated tool that assesses the GitLab CIS benchmarks against a project.",
"version": "1.4.1",
"project_urls": {
"changelog": "https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/tree/main/CHANGELOG.md",
"documentation": "https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/tree/main/docs",
"download": "https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/releases",
"homepage": "https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/",
"issues": "https://gitlab.com/gitlab-org/govern/compliance/engineering/cis/gitlabcis/-/issues"
},
"split_keywords": [
"gitlab benchmarks",
" cis benchmarks",
" gitlab hardening",
" gitlab recommendations",
" gitlabcis",
" gitlab cis benchmarks",
" gitlabcis",
" gitlab",
" cis",
" benchmark scanner",
" gitlab cis benchmark scanner",
" gitlab cis"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f88a70e061e0dada51056fbb9181a5b8c266a244e2074727d88e0b661cb29d82",
"md5": "0321b4a721ea48f93e7fb51d7c37b25e",
"sha256": "e878ba5bb83b632748a6325e5d2f7df7441e377946290a0d0d312f384e932c3a"
},
"downloads": -1,
"filename": "gitlabcis-1.4.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "0321b4a721ea48f93e7fb51d7c37b25e",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 256808,
"upload_time": "2024-11-21T01:56:43",
"upload_time_iso_8601": "2024-11-21T01:56:43.904188Z",
"url": "https://files.pythonhosted.org/packages/f8/8a/70e061e0dada51056fbb9181a5b8c266a244e2074727d88e0b661cb29d82/gitlabcis-1.4.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "bdd64a6c246c0d3b34e2665774e3b0040f811ceb413da8f3cb1385123b1485af",
"md5": "86b650ce6833d19d97e239f154ec2b05",
"sha256": "a3558b74aaa13165b38063af842a4b361847355d1756cdd98e4bcef9d71d6591"
},
"downloads": -1,
"filename": "gitlabcis-1.4.1.tar.gz",
"has_sig": false,
"md5_digest": "86b650ce6833d19d97e239f154ec2b05",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 545541,
"upload_time": "2024-11-21T01:56:45",
"upload_time_iso_8601": "2024-11-21T01:56:45.948590Z",
"url": "https://files.pythonhosted.org/packages/bd/d6/4a6c246c0d3b34e2665774e3b0040f811ceb413da8f3cb1385123b1485af/gitlabcis-1.4.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-11-21 01:56:45",
"github": false,
"gitlab": true,
"bitbucket": false,
"codeberg": false,
"gitlab_user": "gitlab-org",
"gitlab_project": "govern",
"lcname": "gitlabcis"
}