Docker Hub Pull Limit Lint
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Finds every anonymous Docker Hub pull in GitHub Actions, compose, GitLab CI, Kubernetes and Dockerfiles, including the service containers your login step never covers. Docker Hub limit: 100 pulls per 6 hours per IPv4 address or IPv6 /64 subnet (docs.docker.com, checked 2026-09-27).
Install
docker-hub-pull-limit-lint file
Node 18+. The same 10 rules as the VS Code extension, from a terminal or CI.
Free
- Lint the open workflow, compose, GitLab CI, Kubernetes or Dockerfile and see every anonymous Docker Hub pull with line and fix, using all 10 rules.
--ruleslists every rule
With a licence ($29 once)
- Scan the whole workspace in one run and export a Markdown pull inventory report to attach to the CI ticket.
docker-hub-pull-limit-lint --dir ./templates --report html --out report.html
Docker Pro costs $9 per user per month billed yearly ($108 a year), and it only lifts the limit for pulls that log in; this lint costs $29 once.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "docker-hub-pull-limit-lint": { "command": "docker-hub-pull-limit-lint", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Docker Hub Pull Limit Lint
run: pip install rulestamp-docker-hub-pull-limit-lint && docker-hub-pull-limit-lint --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-docker-hub-pull-limit-lint
docker-hub-pull-limit-lint --help
Metadata
Release files for rulestamp-docker-hub-pull-limit-lint 1.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 | |
|---|---|---|---|---|
| rulestamp_docker_hub_pull_limit_lint-1.0.2.tar.gz | 17.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rulestamp_docker_hub_pull_limit_lint-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.5 kB
Release files / rulestamp_docker_hub_pull_limit_lint-1.0.2.tar.gz
| Download URL | rulestamp_docker_hub_pull_limit_lint-1.0.2.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d1fad7c4e99cc8f4d69919435b297e703ae62434e589bd8494e6362c8e711df
|
|
BLAKE2b-256 checksum How to use checksums |
914438a45d218f7735725e88811fc7e865b8317cea6e4f22f4150de4c978eaa6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_docker_hub_pull_limit_lint-1.0.2-py3-none-any.whl
| Download URL | rulestamp_docker_hub_pull_limit_lint-1.0.2-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8b8da94811797db997f2299e4d2844ac6808c6758522551eeb3d2f4446c166e
|
|
BLAKE2b-256 checksum How to use checksums |
0c728fd7bba82f7f9205deb7b376b92e0818d684658c0d3a56d3437ad7b096d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-docker-hub-pull-limit-lint 1.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.