Package Health/vladislavenasty/my-package

vladislavenasty/my-package

The package has a clear MIT license and no install-time scripts, but its artifact lacks a README for consumers. The single-release history, minimal repository activity, and repository/package name mismatch provide too little evidence of durable maintenance.

Latest 0.0.1

Packagist

38%

Total Score

Maturity

Supply Chain

Health Score Breakdown

Release history

Only one release exists, published about 20 months ago, with no releases in the last 12 months. That leaves substantial uncertainty about ongoing maintenance.

Package scaffolding

The package has no README, which weakens consumer transparency for a small library. Missing tests and a changelog are normal in published artifacts and are not concerns by themselves.

Repo package mention

The repository name does not match the package name, and no README mention was available. The source may therefore not clearly belong to this package, which weakens provenance confidence.

Repo popularity

The repository has zero stars and forks and one watcher, offering no supporting evidence of community use or review. Popularity is only supporting evidence, so this is a minor concern.

Repo tooling

Composer is used for builds, but no security scanning tools are present. This is a hygiene gap rather than evidence that the release is unsafe to depend on.