giaphiep/post

Release historydanger

The latest release was published in November 2017, with no releases in the last 12 months despite the package being over eight years old. This is strong evidence of abandonment risk.

Project backingcaution

The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides less visible institutional backing for a project that has not been maintained for years.

Repo issue activitycaution

There are no open issues or pull requests and no issue or pull-request activity in the last month. Combined with the old last push, this supports a lack of ongoing maintenance.

Repo popularitycaution

The repository has one star and no forks, indicating very limited external adoption. Popularity is supporting evidence rather than decisive, but it provides little confidence that issues will be found or supported.

Repo toolingcaution

Composer is used for builds, but no security scanning tooling is present. This is a modest transparency and hygiene gap, not a standalone dependency risk.