juffalow/finstatclient

Release historydanger

The package has had only two releases, both in January 2017, with no release in roughly nine years. That strongly suggests abandonment risk for a client library.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, following years without a new release. This is the strongest ongoing-maintenance concern.

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base for continuity, although the linked repository identifies the same individual as the project owner.

Repo issue activitycaution

There are no open issues or pull requests and no recent activity. While this may indicate a quiet small project, it provides no evidence of current maintenance.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than proof of an unsafe release.