The project has only a five-file tree, one open issue, and no security policy or automated scanning. Its simple dependency profile and clear README reduce adoption friction, but do not offset the prolonged inactivity.
43%
Total Score
50
100
75
75
The latest release was in November 2020, with no releases in the last 12 months and a median interval of about 15 months. This indicates a prolonged maintenance gap for a package developers may still depend on.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history and indicating no observed current maintenance.
The repository name does not match the package name and its README does not mention the package, so the linkage is not clearly demonstrated and transparency is reduced.
The repository has 1 star and 3 forks, providing little evidence of a broad user or maintainer community. Low popularity is supporting caution rather than a verdict on its own.
No security policy is present, and repo_tooling also reports no security-scanning tools. This leaves vulnerability reporting and security practices undocumented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
barberry/interfaces Version ^2.0 | — | — |
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.