omeka/omeka-s
Clear documentation, tests, release notes, and licensing make this straightforward to operate and evaluate. The workflow lacks explicit top-level permissions and security scanning, but active organizational maintenance substantially offsets those hygiene gaps.
88%
Total Score
100
100
94
83
Health Score Breakdown
Composer is used for builds, but no security-scanning tool was detected. This is a modest repository hygiene gap, not evidence that the release is unsafe or abandoned.
The only workflow has no top-level token permissions declaration. Although it requests no detected top-level write permissions, explicitly declaring least-privilege permissions would improve workflow hygiene.
Vulnerabilities
| Title | Versions | Severity |
|---|---|---|
CVE-2023-4157 omeka/omeka-s is vulnerable to Improper Input Validation in versions 0.0.0 - 4.0.3. | 0.0.0 - 4.0.3 | Medium |
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ml/json-ld Version ^1.1 | — | — |
fileeye/pel Version ^0.12.0 | — | — |
doctrine/orm Version ^2.11.2 | — | — |
doctrine/dbal Version ^2.13.8 | — | — |
doctrine/cache Version ^1.12.1 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 11 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.