A single maintainer, no security scanning, and no recent repository activity reduce confidence in ongoing care. The package is licensed, directly matches its repository, and has a stable release history without deprecation.
58%
Total Score
50
100
88
75
Only one registry publishing account is listed, leaving a thin publishing base. The linked repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
The latest release was about three and a half years ago, with no releases in the last 12 months. That is a meaningful maintenance concern despite 25 total releases.
The repository recorded no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates stalled maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance weakness, not evidence of maliciousness.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
douggonsouza/language Version ^1.0.0 | — | — |
douggonsouza/propertys Version ^1.0.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.