EricAI local-models installation guard
The Ericsson ericai-local-models provider is distributed through Ericsson's
authenticated internal Python package repository.
This public distribution provides installation guidance for people who
accidentally resolve ericai-local-models from public PyPI. Its purpose is to
reduce the risk of dependency-confusion attacks against that distribution name.
Behavior
- Importing
ericai_local_modelsor its submodules raisesImportErrorwith instructions for obtaining the internal provider. ericai-local-models-guardandpython -m ericai_local_models_installation_guardprint those instructions and exit with status 1.- Installation succeeds, including with the
mlxextra. The guard has no runtime dependencies and the extra installs no model runtime.
The guard makes no network requests, reads no credentials, and does not download
or run models. It registers no EricAI provider and installs no ericai package
or ericai CLI command. It can coexist with the base EricAI installation guard.
Getting the provider
Ericsson users should follow the internal EricAI installation guide to configure
the approved package indexes and authenticate to the package repository. After
correcting the indexes, reinstall ericai-local-models using
uv pip install --reinstall with the index options from that guide. To install
the full internal client with its provider, use ericai[local_models] with those
same approved indexes.
Security scope
PyPI normalizes ericai-local-models and ericai_local_models to the same
distribution name. This guard does not protect other names, misspellings, or a
compromised publisher account. A low public version does not replace correct
package-index configuration.
Metadata
Release files for ericai-local-models 0.0.1
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 |
|---|---|---|---|---|
| ericai_local_models-0.0.1.tar.gz | 2.9 kB | Without provenance | Details for ericai_local_models-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ericai_local_models-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for ericai_local_models-0.0.1-py3-none-any.whl |
Total release size: 6.6 kB
Release files / ericai_local_models-0.0.1.tar.gz
| Download URL | ericai_local_models-0.0.1.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
089c28036a24607770e8582f7351191a5e2c7bd7814e21e6b1bdfcc30d81d32e
|
|
BLAKE2b-256 checksum How to use checksums |
ecd6f93c22a4c5e117b87242bc205362720bf6e9ac82f2ed2cff6664e38a534a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ericai_local_models-0.0.1-py3-none-any.whl
| Download URL | ericai_local_models-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdfa03204142e3c92c815b5631cd1915b00279a95d8d344d8eef9a3da4a16d37
|
|
BLAKE2b-256 checksum How to use checksums |
be95e071fab70777bcbef70a64a343cde48ada2cff8edb1e10db3aac03b299da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ericai-local-models 0.0.1
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.