rabsana/exchanger

Release historydanger

The package has only two releases, with the latest published about three years ago and none in the last 12 months. This is strong evidence of stagnant maintenance for a library connecting to changing exchange APIs.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The non-archived status does not compensate for the observed lack of recent work.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no external adoption signal. Popularity is only supporting evidence, so this modestly reduces confidence rather than deciding the assessment.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest process gap for a package handling exchange integrations.

Security policycaution

The repository has no security policy, so consumers have no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is less severe than the maintenance stagnation.