Documentation is thorough and the package is clearly tied to its organization-owned repository. CI is complete but uses four unpinned actions, and no security scanning or policy is present.
60%
Total Score
50
50
50
The package has only one release, published 484 days ago, with no releases in the last 12 months. That leaves limited evidence of an ongoing maintenance cycle.
The repository recorded zero commits and zero active maintainers in the last three months. The repository is not archived, but recent maintenance activity is absent.
Composer build tooling is present, but no security scanning tools were detected. This weakens automated assurance without indicating abandonment on its own.
The linked repository has no security policy. This is a transparency gap for reporting and handling vulnerabilities, though the package remains clearly backed by an organization-owned repository.
The single workflow was fully analyzed with no untrusted checkouts or injection findings, but all four action references are unpinned. This is a moderate reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker-demo/service-product Version ^1.0.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.