jbzoo/composer-diff
The project includes repository tests, release notes for this version, and two active contributors behind an organization-owned repository. The main reservations are fully unpinned workflow actions and no published security policy.
82%
Total Score
100
100
94
75
Health Score Breakdown
The project uses Make, Composer, and Box for builds, supporting a structured release process. No security scanning tools were detected, leaving a modest supply-chain hygiene gap.
The repository has no SECURITY.md or other detected security policy, reducing transparency about vulnerability reporting and response expectations.
The single workflow was fully analyzed, uses read-only permissions, and has no dangerous triggers or audit findings. However, all 13 action references are unpinned, leaving workflow dependencies exposed to moving revisions.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Denis Smetannikov |
| David Jonas |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jbzoo/cli Version ^8.0 | — | — |
jbzoo/data Version ^8.0 | — | — |
jbzoo/markdown Version ^8.0 | — | — |
composer/semver Version >=3.0 | — | — |
symfony/console Version >=7.3.4 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 6 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.