Long-term maintenance is not yet demonstrated. Consumer documentation and repository security safeguards are limited, while the MIT declaration and unarchived source repository provide useful positives.
68%
Total Score
100
79
50
The published artifact has no README, making integration harder for a library consumers must use; absent tests and changelog files are normal packaging practice and are not treated as gaps.
The package was first released today and has three releases within hours, showing active initial publishing but no history from which to judge durability.
The repository name does not match the package name, and no README mention was available, so ownership of the published package is less clearly documented.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented; this is a transparency gap but not a severe dependency risk by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
niangpro/core Version self.version | — | — |
niangpro/queue Version self.version | — | — |
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.