bricre/amazon-selling-partner-sdk-listings-items

Release historydanger

The package has only one release, published about 5 years ago, with no releases in the last 12 months. That leaves consumers without evidence of ongoing maintenance or updates.

Repo commit activitydanger

There were 0 commits and 0 active maintainers in the last 3 months, indicating no current development activity. This materially increases abandonment risk for a client tied to a changing external API.

Repo popularitycaution

The repository has 1 star, 0 forks, and 1 watcher, providing little supporting evidence of community adoption or review. Low popularity alone is not decisive, but it offers no compensation for the inactive release history.

Repo toolingcaution

Composer is used for the build, but no security-scanning tools are configured. The missing scanning reduces repository hygiene and transparency, though it is secondary to the maintenance gap.

Security policycaution

The repository has no security policy. For a small generated API client this is a modest transparency gap, but it provides no documented process for reporting or handling vulnerabilities.