The MIT license, included tests, and organization-owned repository provide useful maintenance and transparency signals. Release activity stopped over three years ago, and recent repository activity is also absent. Workflow references are all unpinned, adding a smaller supply-chain hygiene concern.
58%
Total Score
83
100
88
75
The package has had only two releases, with the latest published in January 2023 and none in over three years. The active, non-archived repository partly compensates, but the registry history still indicates stalled maintenance.
There were no commits and no active maintainers in the three months measured. The January 2025 push shows some older activity, but the recent inactivity raises abandonment risk.
The repository uses Make and Composer for builds, but no security-scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence of unsafe code.
The repository has no security policy. That weakens disclosure transparency, although it does not by itself indicate that the package is unsafe to depend on.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all three referenced actions are unpinned, leaving a supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.9.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.