bricre/amazon-selling-partner-sdk-shipping

Release historydanger

The package has only one release, published about five years ago, with no releases in the last 12 months. That is a substantial concern for a client tied to an evolving external API.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package having been abandoned since its initial release. No provided maintenance signal compensates for that inactivity.

Maintainerscaution

Only one registry account has publishing access. The organization-backed repository provides some continuity context, but there is still a thin publishing base if that maintainer becomes unavailable.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The absence of scanning lowers confidence in ongoing maintenance hygiene.

Security policycaution

The repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a transparency gap, though it is less severe than the long-standing inactivity.