ktc/cdn

Release historydanger

The latest release was published in December 2017, with no releases in the last 12 months. This long period without updates is a substantial abandonment concern for a framework integration package.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, consistent with the release history showing that development stopped about 8 years and 10 months ago.

Project backingcaution

The repository is owned by a personal GitHub account rather than an organization, so there is no organizational backing signal to compensate for the inactive development history.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than decisive, but these values provide no community buffer for the lack of maintenance.

Repo toolingcaution

The repository uses Composer, which fits the package ecosystem, but has no security scanning tooling. This is a hygiene gap that adds little protection to an already inactive project.