aklump/json-schema-validation

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, consistent with roughly a year without visible updates. This materially increases maintenance and abandonment risk.

Project backingcaution

The repository is owned by an individual account rather than an organization. This is not inherently unhealthy, but it provides less visible institutional backing for a project with only one registry maintainer.

Release historycaution

The package has 12 releases over about 14 months but only one release in the last 12 months, indicating a notably slow recent cadence. The release history shows activity rather than complete abandonment, which limits the concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. The missing scanning reduces repository hygiene without indicating that the package is unsafe by itself.

Security policycaution

The repository has no security policy. That weakens the project's documented process for receiving and handling vulnerability reports.