Organizational backing, a matching repository, and included tests support continued maintenance. Unpinned workflow actions, no security scanning, and no release since January 2023 add real caution.
64%
Total Score
75
100
88
67
The package has had only three releases and none in the last 12 months, with the latest in January 2023. The repository was pushed more recently, which partly offsets but does not remove the release-staleness concern.
There were no commits and no active maintainers in the measured three-month period. The more recent repository push partly compensates, but current development activity remains uncertain.
The repository uses Make and Composer, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.
No security policy is present in the repository, leaving vulnerability-reporting expectations undocumented.
The single workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but all three action references are unpinned. That leaves avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gift-card 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.