digipolisgent/robo-digipolis-general
There is no security policy or automated security scanning, which limits transparency for a dependency. The MIT license, tested source tree, and organization-backed repository provide useful safeguards.
62%
Total Score
75
100
88
75
Health Score Breakdown
The package has 18 releases since February 2017, but none in the last 12 months; the latest release was about one year ago. Its long history partly offsets the recent inactivity.
There were zero commits and zero active maintainers in the last 3 months. Combined with the absent releases over the last 12 months, this indicates slowed maintenance.
The repository uses Composer and Robo for its build, but no security scanning tools are configured. This weakens automated oversight without making the package unfit by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a dependency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Dieter Blomme |
| Jelle Sebreghts |
| Peter Decuyper |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ckr/arraymerger Version ^3.0 | — | — |
consolidation/robo Version ^4.0 || ^5.0 | — | — |
grasmash/yaml-expander Version ^3 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 9 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.