tokenly/crypto-quantity

Release historydanger

The package has 10 releases since 2016, but its latest release was about eight years ago and there have been no releases in the last 12 months, indicating likely abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with maintenance having stopped and increasing the risk that compatibility issues will remain unresolved.

Repo toolingcaution

Composer is used for the build, but no security-scanning tool was found; this is a modest transparency and maintenance gap rather than evidence of unsafe code.

Repository archivedcaution

The repository is not archived, which preserves a path for maintenance, although its last push was nearly seven years ago and does not offset the stale release history.

Security policycaution

The repository has no security policy, so users have no documented process for reporting vulnerabilities or receiving security guidance.