Package Health/dimvilkester/composer-example-package

dimvilkester/composer-example-package

Risky to adopt: the package has had no release or repository activity for about 9 years and has only two releases. Its repository does not match the package name, and the published artifact has no README, leaving ownership and usage guidance unclear.

Latest 1.0.1

Packagist

35%

Total Score

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in June 2017, with no release in about 9 years and none in the last 12 months. This is strong evidence of abandonment risk despite the stable 1.0.1 version.

Repository archived

The repository is not formally archived, which is a positive, but it was last pushed in June 2017. The lack of activity for about 9 years substantially outweighs the non-archived status.

Package scaffolding

The package has no README, while its source repository also has no tests or changelog. Missing tests and changelog are acceptable in a published artifact, but the absent README is a real transparency and consumer-guidance gap for this library.

Repo package mention

The linked repository name does not match the package name, and no README mention was found. A name mismatch can be normal for a sub-package, but here the absence of a confirming mention leaves package ownership less clear.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external indication of adoption or community support alongside the long inactivity.