This release appears usable and reasonably transparent: it is MIT-licensed, has a complete source tree with tests and documentation, has a stable v1.0.5 release, is not deprecated or archived, and has recent release and repository activity. The main concerns are the very small maintenance base—one maintainer and one contributor responsible for all recent commits—along with low repository adoption and the absence of a security policy or automated security scanning. Overall, it is a viable dependency for developers comfortable with the risk of relying on a young, single-maintainer package, but it does not yet demonstrate the maturity or redundancy of a highly established library.
72%
Total Score
50
100
89
90
Only one registry account, yangweijie, has publish access. This is a genuine continuity concern for a user-owned project, though repository activity shows the same maintainer is currently active.
The repository is owned by an individual user rather than an organization, so there is no organizational maintenance redundancy to offset the concentrated contributor base.
One contributor made 100% of the two recent commits, creating a concentrated bus factor and increasing continuity risk for this user-owned repository.
There were two commits in the last three months from one active maintainer, showing recent maintenance but a relatively low maintenance cadence for a young package.
There are no open issues or pull requests and no recent issue or pull-request activity. This avoids an unresolved-maintenance backlog, but it also provides little evidence of an active user or contributor community.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.