devscreencast/json-response

Release historydanger

The package has only two releases, both published on the same day in April 2017, with no releases in the last 12 months. This is strong evidence of prolonged inactivity for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long gap since the last release and raising abandonment risk.

Repo popularitycaution

The repository has nine stars and four forks, indicating a small user and contributor footprint. Popularity is supporting evidence only, so this modestly reinforces rather than determines the assessment.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are present. This is a modest transparency gap, secondary to the much stronger maintenance concern.

Security policycaution

The repository has no security policy, leaving vulnerability reporting expectations undocumented. This lowers transparency but is not severe on its own.