0.0.1/try-make-package

Risky to depend on: the package has had no release or repository activity for over eight years and provides almost no project documentation. It is not deprecated or archived, but its tiny, inactive project and missing license make adoption a liability.

Latest 0.0.2

Packagist

30%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both published over eight years ago, with no releases in the last 12 months. This is strong evidence of abandonment rather than an actively maintained dependency.

Repo commit activity

The repository has had zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.

License

Neither a registry license declaration nor a license file was found in the package or repository. This creates a real legal and transparency concern for adoption.

Package scaffolding

The artifact includes a very short README, but no tests or changelog; the missing tests and changelog are not themselves packaging defects, while the minimal README provides little guidance for consumers.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no meaningful evidence of community validation.