sainsburys/sainsburys-http-service

Release historydanger

The last release was in January 2016, about 10 years and 8 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having a clear release history.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, following a last push about 9 years and 8 months ago. That leaves little evidence of current capacity to fix defects or track ecosystem changes.

Repo toolingcaution

Composer is used for builds, but no security-scanning tool was detected. The missing scanning is a modest repository-hygiene gap, while the build tooling itself is appropriate for the package.

Security policycaution

No repository security policy was detected, leaving vulnerability-reporting expectations unclear. This is a transparency gap, but it is less significant than the package's prolonged inactivity.