wubbajack/filecrypt
Documentation, tests, and an MIT license provide useful basics. The single runtime dependency keeps installation simple, but no security policy is published for this encryption-focused library.
42%
Total Score
100
75
75
Health Score Breakdown
The latest registry release was published in January 2016, with no releases in the last 12 months. This long period without a release is strong evidence of abandonment risk, despite the package not being marked deprecated.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was in January 2016 and does not offset the stale release history.
The linked repository has no security policy. For a package implementing file encryption, this is a meaningful transparency and maintenance gap.
Version 0.2.0 is not a stable major release, which is consistent with limited maturity and increases the risk of API changes if development resumes.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Christopher Stolk |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.