sprypradeep/yii2-braintree

Release historydanger

The package has only two releases, both published in May 2016, and none in the last 12 months. This long period without releases is strong evidence of abandonment for an integration package.

Repo commit activitydanger

The repository has had zero commits and zero active maintainers in the last three months, while its last push was in 2016. The inactive source reinforces the release-history concern.

Package file treecaution

The artifact and repository each contain only three files: the implementation, README, and Composer manifest. This is not inherently unsafe, but it offers little project evidence or maintenance structure for a payment integration.

Repo popularitycaution

The repository has one star and two forks, indicating very limited adoption. Popularity is only supporting evidence, but here it provides no meaningful counterweight to the long inactivity period.

Repo toolingcaution

Composer is used for the build, which is appropriate, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence of malicious behavior.