jrsaunders/bacs

Release historydanger

The last release was in September 2017, and there have been no releases in roughly nine years. The package had a short early release history but shows no current maintenance cadence.

Repo commit activitydanger

There were no commits and no active maintainers in the three months measured, consistent with the repository having stopped changing around September 2017. This is strong evidence of abandonment risk.

Licensecaution

The manifest declares a proprietary license, with no detected license text or license file in the package or repository. This leaves redistribution and reuse rights unclear for an open-source dependency.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. That is a modest transparency and maintenance gap, while the small codebase limits its practical weight.

Security policycaution

The repository has no security policy. For a small, inactive package this reduces the available path for reporting issues, though it is secondary to the lack of maintenance.