The package has a clear README, an MIT declaration, release notes for this version, and no install-time scripts. Its very small four-file tree, single publisher, and absent security scanning provide limited evidence of ongoing project capacity.
42%
Total Score
25
100
81
75
The package has only three releases, with none in the last 12 months and a latest release in August 2017. This long release gap is strong evidence of abandonment risk.
The repository recorded no commits or active maintainers in the last three months, consistent with the long release gap. This materially lowers confidence in ongoing maintenance.
Only one registry account has publish access, giving the package a thin publishing base. Because the project is user-owned and there is also no recent activity, this adds to maintenance risk.
Composer is used for the build, but no security scanning tools are present. This is a modest supply-chain hygiene gap rather than evidence that the release is unsafe.
The linked repository has no security policy. For a small, inactive plugin this is a transparency gap, though it is less significant than the maintenance evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spress/spress-installer 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.