bryangruneberg/slail

Release historydanger

This is the package's only release, published about 8 years ago, with no releases in the last 12 months. That strongly raises abandonment risk despite the repository still being available.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months. Combined with the old sole release, this is meaningful evidence of inactive maintenance.

Lifecycle scriptscaution

The package defines a post-create-project-cmd lifecycle script. This deserves some installation scrutiny because it runs automatically, but the signal alone does not show harmful behavior or make the release unfit.

Repository archivedcaution

The repository is not archived, which preserves a path for maintenance, but its last push was about 4 years ago and does not compensate for the stale release history.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less severe than evidence of active security problems.