meser10/api-client

Release historycaution

The package is newly published, with two releases on the same day and no established release history. This limits evidence of sustained maintenance, though the rapid second release shows active initial development.

Repo commit activitycaution

There were no commits or active maintainers in the last three months. Because the package is only hours old, this is mainly a coverage gap rather than evidence of abandonment, but sustained maintenance is unproven.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. That is a modest transparency and maintenance gap for a package handling API credentials.

Security policycaution

The repository has no security policy, leaving disclosure and response expectations undocumented.

Workflow auditcaution

The single workflow is fully analyzed and uses read-only permissions, with no audit findings or untrusted checkout paths. Both action references are unpinned, which weakens build reproducibility and update safety.