bespoke-support/distance

Release historydanger

The package has only two releases, with no releases in the last 12 months and a latest release in September 2018. This long release gap is strong evidence of abandonment risk, though the package is not deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since September 2018.

Package scaffoldingcaution

The package includes a README and published release notes, but the README is only 11 characters and the project has no tests or changelog. The missing tests and changelog are not themselves packaging failures, while the extremely limited documentation weakens transparency.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a modest maintenance and assurance gap for a package that has otherwise seen no recent activity.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a transparency gap, especially alongside the lack of recent maintenance.