govtech-csg-xcg-dangerousrequests
This package belongs to the eXtended Code Guardrails (XCG) project, which consists of a series of packages that harden the Django web framework to prevent common web application vulnerabilities.
The Dangerous Requests package contains a Django app that protects your application against dangerous requests. More specifically, this package protects against SSRF attempts when you use the requests library in your application. This is achieved by (transparently) leveraging on the advocate library under the hood.
Do note that the README in this repository is intentionally limited in scope and is catered towards developers. For detailed instructions on installation, usage, and community guidelines, please refer to the published documentation at https://xcg.tech.gov.sg.
Security-related matters
For instructions on how to report a vulnerability, refer to the official documentation website.
Additionally, enable email alerts for security issues by "watching" this repository. The "watch" button can be found near the top right corner of this repo's home page, and there are various options for configuring notification volume. To receive security alerts, either enable notifications for "All Activity" or "Custom -> Security alerts".
Installing development dependencies
Before building or testing the package, or committing changes, install the development dependencies into a virtual environment:
# In the project root directory
python -m venv .venv && source .venv/bin/activate
pip install -r requirements-dev.txt
Building
The package can be built using build as the build frontend and setuptools as the build backend.
Run the build command below:
# In the project root directory
python -m build .
This creates a directory named dist/, which should contain 2 files:
- A
.whl(wheel) file, which is a binary distribution format for Python packages - A
.tar.gzfile, which is a source distribution format for Python packages
To view the source files included in the source distribution, use the tar utility as follows:
tar --list -f dist/<filename>.tar.gz
To install the package directly from either distribution files:
pip install <name_of_distribution_file>
Testing
As the tests for this package use multiple variants of the Django settings module, a convenience script has been provided for ease of running all test methods. Execute the tests using the commands below:
pip install -e . # Performs an "editable install" of the govtech-csg-xcg-dangerousrequests package
cd tests/
DANGEROUS_REQUESTS_RUN_FLAKY_TESTS=true /bin/bash run_all_tests.sh
Note on potentially flaky tests
There are a few test methods within the test suite that make HTTP requests over the internet. These are non-ideal from an automated testing perspective as they can fail intermittently due to issues such as network error.
Until these are replaced with better means of testing, developers can choose to skip those tests by dropping DANGEROUS_REQUESTS_RUN_FLAKY_TESTS=true from the command given above.
Running pre-commit hooks
Note: This section is only relevant if you intend to contribute code
This project uses the pre-commit tool to run Git pre-commit hooks for linting and code quality checks. The pre-commit tool itself should have been installed along with the development dependencies. After cloning the repository for the first time, run the command below to "install" the Git hooks:
pre-commit install
The command above creates a file .git/hooks/pre-commit, which defines the shell commands to run before any Git commit is created.
Subsequently, any invocation of git commit will trigger the commands, rejecting the commit if there are linting errors. Issues should be automatically fixed, but you will need to re-stage the changes before attempting the commit again.
For a list of hooks run by pre-commit, see its configuration file.
Metadata
Release files for govtech-csg-xcg-dangerousrequests 0.1.0
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 |
|---|---|---|---|---|
| govtech-csg-xcg-dangerousrequests-0.1.0.tar.gz | 30.3 kB | Without provenance | Details for govtech-csg-xcg-dangerousrequests-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| govtech_csg_xcg_dangerousrequests-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for govtech_csg_xcg_dangerousrequests-0.1.0-py3-none-any.whl |
Total release size: 55.9 kB
Release files / govtech-csg-xcg-dangerousrequests-0.1.0.tar.gz
| Download URL | govtech-csg-xcg-dangerousrequests-0.1.0.tar.gz |
|---|---|
| Size | 30.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91c51c19970da1e98cd1c774ca16bf20a916fbb7491090bb7465b59d641eea02
|
|
BLAKE2b-256 checksum How to use checksums |
4faaf48192c9cd79d57be559c4dc04e15231f607143fa93b1756d880c9068002
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Release files / govtech_csg_xcg_dangerousrequests-0.1.0-py3-none-any.whl
| Download URL | govtech_csg_xcg_dangerousrequests-0.1.0-py3-none-any.whl |
|---|---|
| Size | 25.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f1b268112828801daf75d8f20af6689bcc78c32db5b01561d91cbec3208948a
|
|
BLAKE2b-256 checksum How to use checksums |
f94be275e95eac2a6178b57fa0410494f02746717abf6f33fb338267cd51f604
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for govtech-csg-xcg-dangerousrequests 0.1.0
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.