should-type-adaptors

Release historydanger

The package has had no release in more than eight years, with only three releases overall and none in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in November 2019. The long period without observed development materially lowers confidence in ongoing maintenance.

Lifecycle scriptscaution

The package uses a prepublish lifecycle script. This adds some install and publication complexity, though the signal does not show a dangerous install-time script.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package, so the connection between the artifact and repository is less transparent. The organization-owned repository provides some context but does not resolve that gap.

Security policycaution

The repository has no security policy, leaving no documented security reporting or response process. This is a hygiene and transparency concern, not evidence that the package is malicious.