digihum/omeka-project-100daysorguk

Release historydanger

The package has only two releases, both published on the same day, and none in the last 12 months; the latest release is nearly three years old. This is strong evidence of abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the repository's nearly three-year-old last push. This materially increases abandonment risk.

Repo package mentiondanger

The repository name does not match the package name and its README does not mention the package, so the repository may not actually be the package's source. Organization ownership reduces but does not remove this identity concern.

Repo toolingcaution

Composer is used for the build, which is appropriate for this package, but no security scanning tooling is present. The missing scanning is a secondary hygiene gap rather than evidence of abandonment by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package with no recent maintenance evidence.