mooring-spacy-en-md
A thin companion package that vendors the MIT-licensed spaCy en_core_web_md
model so mooring's offline PII name/organisation
detection works in PyPI-only / air-gapped environments.
Why it exists
mooring's default name-detection model (GLiNER) downloads from Hugging Face, and
spaCy's own models are distributed from GitHub releases — neither reachable in a
locked-down corporate network whose only package channel is an internal PyPI
mirror. The en_core_web_md pipeline is MIT-licensed, so this package republishes
its model directory as ordinary PyPI package data, the one channel such teams
have. No Hugging Face, no GitHub, no model mirror at install time.
You don't install this directly — pip install mooring[pii-spacy] pulls it in,
then set [ai.pii] name_backend = "spacy" in your mooring config.
For maintainers: vendoring the model before a release
The model bytes are not committed to git (they're ~40 MB). On a machine that can reach the model once:
pip install "spacy>=3.7,<4" en_core_web_md # or: python -m spacy download en_core_web_md
python scripts/vendor_spacy_model.py # exports the model into src/mooring_spacy_en_md/_model/
cd packages/mooring-spacy-en-md && uv build # the wheel now carries the model + its license
uv publish
Keep the spacy pin in mooring's pii-spacy extra compatible with the model's
spaCy version (the vendor script prints it). The model's own license/attribution
ships inside the vendored _model/ directory (its meta.json).
Metadata
Release files for mooring-spacy-en-md 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 |
|---|---|---|---|---|
| mooring_spacy_en_md-0.1.0.tar.gz | 33.5 MB | Without provenance | Details for mooring_spacy_en_md-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mooring_spacy_en_md-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mooring_spacy_en_md-0.1.0-py3-none-any.whl |
Total release size: 67.0 MB
Release files / mooring_spacy_en_md-0.1.0.tar.gz
| Download URL | mooring_spacy_en_md-0.1.0.tar.gz |
|---|---|
| Size | 33.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbfdabafc66a0c77e82fbc0ad2ea55990dda64fe2a37ab1aae717521e4952f67
|
|
BLAKE2b-256 checksum How to use checksums |
8bbe91d63c64cd1f47e707678be91fc148b3d6481c12d2b12fef5fabba3546bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / mooring_spacy_en_md-0.1.0-py3-none-any.whl
| Download URL | mooring_spacy_en_md-0.1.0-py3-none-any.whl |
|---|---|
| Size | 33.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26c5dc4ed2bb8d2aba29c1bfb32b65cdc502287b91e54cfdc866135266a90be4
|
|
BLAKE2b-256 checksum How to use checksums |
0e65cda49a2ea021a3f961b1ab8ebd4f99c4aed0687e5394bbbe833db4240de5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for mooring-spacy-en-md 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.