mylekha/record-api

Release historycaution

This is the package's first registry release, published on the collection date, so there is no release history or cadence demonstrating sustained maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last three months. Because the project is newly published, this is partly explained by its age, but it still leaves maintenance capacity unproven.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap for a package handling authentication, permissions, and API data.

Security policycaution

The repository has no security policy, so users have no documented channel or process for reporting vulnerabilities.

Workflow auditcaution

The complete workflow audit found no injection or high-severity findings, but all four action references are unpinned and the only workflow grants top-level write permissions, weakening build reproducibility and token least privilege.