tokenly/copay-client
The package includes tests, a matching repository, and no install-time scripts. It lacks a security policy and automated security scanning, adding concern for a cryptographic client.
32%
Total Score
50
67
83
Health Score Breakdown
The latest release was in April 2017, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment for a package handling wallet and transaction operations.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and indicating no current maintenance capacity.
Composer build tooling is present, but no security-scanning tools were detected. This leaves the project without observed automated security checks, which matters for a cryptographic client.
The repository is not archived, which avoids the strongest abandonment signal, but its last push was in November 2017 and does not offset the lack of recent release or commit activity.
No security policy was found. That is a meaningful transparency gap for a client handling wallet encryption, signing, and transaction operations.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Devon Weller |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 bitwasp/bitcoin Version ^0.0.30 | — | — |
rmccue/requests Version ^1.6.1|dev-master | — | — |
tokenly/crypto-quantity Version ^1.0 | — | — |
tokenly/counterparty-transaction-composer Version ^1.1.2|dev-master | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.