jleagle/btn-api-client

Release historydanger

The package has had only two releases, with the latest published in September 2015 and none in the past 12 months. This is strong evidence of abandonment risk, although the repository is not archived.

Repo commit activitydanger

There were no commits and no active maintainers in the past three months, consistent with a project that has been inactive for years. This materially increases the risk that defects or compatibility issues will remain unresolved.

Licensecaution

Neither the package metadata, artifact, nor repository contains a recognized license. That creates a material legal and transparency concern for a dependency.

Security policycaution

The repository has no security policy. For a small, inactive API client this is a transparency gap, though it is less serious than the lack of maintenance evidence.

Version stabilitycaution

Version 0.0.2 is not a stable major release, so API compatibility is less predictable for consumers. Its non-prerelease status provides only limited compensation.