imedge/inventory-feature
Usable with caveats: this release is actively published and backed by a non-archived organization repository with tests and a clear package README. Dependence is less reassuring because the project has only one recent contributor, no license file, and limited security-policy and workflow-permission hygiene.
68%
Total Score
67
100
81
80
Health Score Breakdown
No declared license or license file was found in the package or repository, leaving the legal terms for using the dependency unclear.
All recent commit activity comes from one contributor, creating a meaningful continuity risk; organization ownership provides some backing but does not show a second active maintainer in this period.
Only 1 commit was recorded in the last 3 months, indicating limited recent development activity even though the package has continued releasing.
Composer build tooling is present, but no security-scanning tool was detected, leaving a security-process gap that is relevant to supply-chain transparency.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 imedge/db-migration Version >=0.8 | — | — |
imedge/node-provided-libs Version ^0.20-rc | — | — |
Weekly Downloads
Info
- Last Published
- 6 days ago
- Created
- 2 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.