A README, tests, and organization-backed source make the package easier to assess and maintain. Six open issues and no recent work mean future fixes are uncertain.
55%
Total Score
67
100
88
83
The package has 92 releases and historically released about every 5 days, but it has had no release in nearly 5 years. That long publishing gap materially raises abandonment risk.
There were no commits and no active maintainers in the last 3 months, consistent with the nearly 5-year release gap. This is the strongest evidence that fixes may not arrive.
Six issues remain open, with no new or closed issues and no merged pull requests in the last month. The unresolved backlog reinforces the maintenance concern.
Composer is used for the build, but no security scanning tools are present. This is a modest transparency and maintenance gap rather than a decisive risk.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This matters more because the package appears inactive.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pluf/user Version 6.x | — | — |
pluf/tenant Version 6.x | — | — |
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.