The repository is backed by an organization and the package includes clear documentation, a license, and release notes. Recent activity is narrow, with two commits from one automated contributor in three months, and its only workflow uses an unpinned action.
78%
Total Score
67
100
94
75
All two recent commits came from one contributor, actions-user, giving the observed maintenance activity a concentrated bus factor. Organization backing partly reduces handoff risk but does not remove the narrow activity signal.
Two commits occurred in the last three months, showing some recent maintenance, but the volume is limited for a package with ongoing releases.
Composer build tooling is present, but no repository 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, leaving vulnerability reporting and response expectations undocumented.
The single workflow uses a pull_request_target trigger, but the audit found no untrusted checkout or script injection and no high- or medium-severity findings. Its one action is unpinned, creating a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
dystcz/dystore-api Version ^1.0.15 | — | — |
illuminate/support Version ^12.0|^13.0 | — | — |
spatie/laravel-newsletter Version ^5.1 | — | — |
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.