jweiland/telephonedirectory
A security policy is absent, and all three workflow actions are unpinned. The organization-backed repository remains active, with recent releases, tests, and release notes supporting continued maintenance.
82%
Total Score
100
100
88
75
Health Score Breakdown
Composer build tooling is present. No security scanning tools were detected, leaving a modest process gap without evidence of abandonment.
The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.
The assessed release is stable and not a prerelease. The reported latest version being 5.0.1 while assessing 6.2.1 is an inconsistency, but it is not enough by itself to indicate abandonment.
The audit analyzed both workflows and found no untrusted checkout or script-injection paths, but all three action references are unpinned and three high-confidence template-injection findings remain in the release workflow. These are workflow hygiene concerns rather than a demonstrated release-blocking risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Stefan Froemken |
| Hoja Mustaffa Abdul Latheef |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jweiland/maps2 Version >=12.0.0 | — | — |
typo3/cms-core Version ^13.4 | — | — |
typo3/cms-fluid Version ^13.4 | — | — |
typo3/cms-backend Version ^13.4 | — | — |
typo3/cms-extbase Version ^13.4 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 8 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.