EricAI installation guard
The Ericsson EricAI client is distributed through Ericsson's authenticated internal package repository.
This public distribution provides installation guidance for people who
accidentally resolve ericai from public PyPI. Its purpose is to reduce the risk
of dependency-confusion attacks against the internal distribution name.
What this package does
ericaiandericai-mcpprint installation guidance and exit with status 1.python -m ericai_installation_guardprints the same guidance and exits with status 1.- Importing
ericai, includingfrom ericai import EricAI, raisesImportErrorexplaining how to obtain the internal client.
The guard has no runtime dependencies. It makes no network requests, reads no credentials, and does not download, install, or authenticate to the internal client. Installing the wheel succeeds; attempting to use it as the client fails.
Getting the client
Ericsson users should follow the internal EricAI installation guide to configure
the approved Python package indexes and authenticate to the package repository.
After correcting the index configuration, reinstall ericai from the internal
repository with uv pip install --reinstall and the guide's index options.
Security scope
This guard addresses the exact distribution name ericai. It does not protect
misspelled names, other distributions, or a compromised publisher account. A low
public version does not replace correct package-index configuration.
1 maintainer
Metadata
1 maintainer
Release files for ericai 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-0.0.1.tar.gz | 2.7 kB | Without provenance | Details for ericai-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ericai-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for ericai-0.0.1-py3-none-any.whl |
Total release size: 6.0 kB
Release files / ericai-0.0.1.tar.gz
| Download URL | ericai-0.0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2de302885840a74932381a7cbe277566527a3541e913ba10105fca23dcd0151a
|
|
BLAKE2b-256 checksum How to use checksums |
a577687708d6671f02e03fe9e36e749d18805670a9ea78a354215484f3b5c5c0
|
| 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-0.0.1-py3-none-any.whl
| Download URL | ericai-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9874d1478b00571bed36cd409eb4701a8911bf0a2f34ea46f526b768edfe107c
|
|
BLAKE2b-256 checksum How to use checksums |
1929f11fe0ee2d017ec1ae67bc154f0872a403cdf4e1c1b858842643d401d9b0
|
| 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 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.
