pessek/hypedropzone
It has clear integration guidance, a matching source repository, and no install-time scripts. The narrow maintainer base and absent security policy add uncertainty for long-term use.
48%
Total Score
50
67
88
Health Score Breakdown
The latest release was published nearly five years ago, with no releases in the last 12 months and only two releases overall. That is substantial abandonment risk for a dependency.
Only one registry account has publish access. This is not proof of poor maintenance, but it leaves limited visible publishing capacity when the project already has a long release gap.
Composer is used for the build, which supports reproducibility, but no security-scanning tooling is reported. This is a modest transparency and maintenance gap.
The repository is not archived, which is a meaningful counterpoint, but its last push was also nearly five years ago and does not offset the stale release history.
The linked repository has no security policy. This weakens vulnerability-reporting transparency, though it is secondary to the much stronger maintenance concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Hermand PESSEK |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 npm-asset/dropzone Version <=5.4.0 || >5.5.0 | — | — |
composer/installers Version ~1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 5 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.