beycanpress/freshbooks

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the long release pause, this indicates weak current maintenance capacity.

Release historycaution

The package has had no release in about 22 months, despite nine releases overall and a previously regular cadence. That extended pause is meaningful abandonment risk for a young 0.x package.

Repo toolingcaution

Composer is used for the build, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than proof of unsafe code.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency and maintenance gap for an API client.

Version stabilitycaution

Version 0.1.10 is not a stable major release, so its API may still change and compatibility expectations are weaker. It is not marked as a prerelease, which partially reduces that concern.