rick20/ibanking

Release historydanger

The package is over 10 years old, with only three releases and none in the last 12 months; its latest release was published in July 2016. This is strong evidence of abandonment for a dependency that interacts with banking services.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the release history showing no activity since July 2016. No provided maintenance signal compensates for this gap.

Licensecaution

Neither the package metadata nor the artifact or repository contains a recognized license. That leaves the legal terms for adopting and redistributing the package unclear.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling is present. This is a modest transparency gap rather than evidence that the release is unsafe on its own.

Security policycaution

The repository has no security policy. This is a transparency and maintenance gap, especially for a package handling bank credentials and account data.