evsmash/core

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement package specified. Package-level deprecation is a severe dependency risk.

Release historydanger

The latest release was published over ten years ago, with no releases in the last 12 months. This is strong evidence of abandonment despite the package having 32 historical releases.

Dependency profilecaution

The package declares 33 runtime dependencies and no development dependencies. This creates a broad, difficult-to-maintain dependency surface for an abandoned package.

Maintainerscaution

Only one account has registry publish access. This is a limited maintenance base, although registry access alone does not prove who actively maintains the code.