spryker/log-extension
The registry history is thin, with only one release and none in the last 12 months. The source project remains active with five recent commits from five contributors and organization backing; workflow pinning and security-policy coverage are modest hygiene gaps.
82%
Total Score
100
83
67
Health Score Breakdown
This package has had only one release, 810 days ago, with none in the last 12 months, which weakens release transparency. Recent repository activity provides compensating evidence that the project is not abandoned.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence of abandonment.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency but is not by itself a severe dependency risk.
The sole workflow was fully analyzed with no audit findings and no dangerous triggers or untrusted checkouts. However, two of four action references are unpinned, so workflow reproducibility has a minor hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/transfer Version ^3.27.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years 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.