asap

Release historydanger

The latest registry release was published in July 2017, with no releases in the last 12 months. This long release gap materially raises maintenance and abandonment concerns.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, limiting publication transparency. The small, dependency-free artifact partly reduces the practical impact of this gap.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, confirming that current maintenance is inactive even though the repository is not archived.

Security policycaution

The repository has no security policy, which weakens vulnerability-reporting transparency. This is a hygiene gap rather than evidence that the package is unsafe.