asm/eprel-api-client

Project backingcaution

The repository is owned by an individual rather than an organization, so the single registry maintainer does not benefit from visible organizational backing.

Release historycaution

Six releases arrived within the first few days, but no later releases are shown through the collection date, leaving roughly six months without a new release. This is a young project, so the gap is a meaningful maintenance concern.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Given the package's young age and the much longer gap since its latest release, this is a meaningful abandonment concern.

Security policycaution

No repository security policy is present. This is a transparency gap, though the available tooling and small project scope partly reduce its weight.

Workflow auditcaution

The only workflow was fully analyzed and has no dangerous triggers, untrusted checkouts, injection findings, or write-wide permissions. However, all three action references are unpinned, leaving avoidable workflow supply-chain exposure.