mygento/ioncube

Release historydanger

The package has only one release, published about 9 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package remaining undepricated.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, while its last push was in April 2017. The long inactivity materially lowers confidence in ongoing maintenance.

Repo popularitycaution

The repository has 0 stars and 0 forks, with only 2 watchers. Popularity is supporting evidence rather than a verdict, but these counts provide no independent sign of active community validation.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling is reported. For a small, long-stagnant package this is a minor transparency and maintenance concern.

Security policycaution

The repository has no security policy, leaving no documented route for reporting vulnerabilities. This adds a modest transparency concern, though it is less significant than the prolonged inactivity.