gridguyz/facebook

Clear licensing and a matching source tree improve transparency, while the small dependency set is manageable. Its sole release was over 12 years ago, with no tests, security policy, or meaningful repository activity, making abandonment the main concern.

Latest 0.6

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published over 12 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a package intended as a maintained dependency.

Project backing

The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This gives some ownership consistency without showing a larger maintenance team.

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 evidence of a broader user or contributor base.

Repo tooling

Composer is used as a build tool, which fits the package ecosystem, but no security scanning tooling is reported. This is a modest transparency and maintenance gap for a package that has otherwise seen little activity.

Repository archived

The linked repository is not archived, which preserves a path for maintenance. However, its last push was over 12 years ago, so the unarchived status does not demonstrate active support.