akansh/amazon

The MIT license and absence of install-time scripts reduce adoption friction. The project has little supporting process, so plan for compatibility and fixes to be your responsibility.

Latest 0.2

Packagist

38%

Total Score

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in 2019, with no releases in the last 12 months. The long period without a new release is strong evidence of abandonment risk.

Package scaffolding

The library artifact has no README, which makes integration harder, while the absence of tests and a changelog in the published package is normal packaging practice. A GitHub release exists for this version, providing some release traceability.

Repo popularity

The repository has zero stars and zero forks, with one watcher. This provides little community evidence or external validation, though popularity is supporting evidence rather than a verdict.

Repo tooling

Composer is used for the build, but no security-scanning tooling is present. The missing scanning is a hygiene gap for a library with no recent maintenance evidence.

Security policy

The repository has no security policy. This weakens disclosure transparency, though it is less important than the package's long-term maintenance gap.