bricre/amazon-selling-partner-sdk-vendor-direct-fulfillment-transactions

Release historydanger

There has been only one release, published over five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for an API client that may need updates as the upstream service changes.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with more than five years without observed updates. This materially raises maintenance and abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and upkeep gap, not evidence of unsafe code by itself.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a maintenance and transparency gap for a dependency handling API credentials.