Package Health

ltsc/container

The package has no license and the repository does not clearly identify the package. Its tiny dependency set and lack of install scripts reduce exposure, but they do not offset the maintenance and transparency concerns.

Latest 1.0-betaPackagistPackagist

35%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

0

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

42

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

50

Health Score Breakdown

Release historydanger

Only one release exists, published about 7 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with its last push being about 7 years ago. This materially raises abandonment risk.

Licensecaution

No declared license, license file, or repository license file was found. That creates a real legal and transparency concern for adoption.

Package scaffoldingcaution

The package has no README, tests, or changelog, although the GitHub release flag provides some release traceability. The missing consumer documentation is still a meaningful gap for a small library.

Repo package mentioncaution

The repository name does not match the package name, and no README mention was available to establish the repository-package relationship. This weakens provenance transparency.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

ErikaEmma

Direct Dependencies

DependencyLast ReleaseScore
psr/container
Version ^1.0
—
—

Weekly Downloads

Info

Last Published
7 years ago
Created
7 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform