hypejunction/forms_api
Its small footprint and single registry maintainer limit resilience if the publisher becomes unavailable. Recent releases, tests, and a non-archived repository are reassuring, but all 11 workflow action references are unpinned and the repository does not clearly identify this package.
68%
Total Score
50
100
86
67
Health Score Breakdown
One registry account has publish access, creating a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided backing signal to compensate for that concentration.
There were no commits and no active maintainers in the three months measured. This conflicts with the recent registry release cadence and lowers confidence in ongoing development between releases.
The repository name does not match the package name and its README does not mention the package, so the source-package relationship is not clearly established by the collected evidence.
Composer is used for builds, but no security-scanning tool was detected. This is a modest transparency and maintenance gap, not evidence of malicious behavior.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 elgg/elgg Version ~7.0.0 | — | — |
composer/installers Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 10 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.