liftup

Release historydanger

The package has had only one release, published over five years ago, with no releases in the last 12 months. The stable version and repository documentation help, but this strongly limits evidence of ongoing maintenance.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for years. Existing tests and organization ownership provide some context but do not demonstrate current maintenance.

Repo toolingcaution

The repository uses a build tool, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The package's clear license and README compensate for general transparency but not this security-process gap.

Workflow auditcaution

The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, both referenced actions are unpinned, which weakens build reproducibility and supply-chain hygiene.