PHPStan rules and type extensions that make the Contempt application model statically verifiable.
65%
Total Score
caution
A young package with one active contributor and an unpinned CI image leaves maintenance and build-reproducibility concerns.
The package is only 46 days old and has five releases clustered within roughly three hours. This shows active initial publishing but provides little evidence of long-term maintenance.
One contributor made all four recent commits, creating a concentrated maintenance dependency. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository recorded four commits in the last three months, indicating some activity, but the volume is limited for a package with only 46 days of history.
No repository security policy is present. This is a transparency gap, though the existing composer-audit tooling provides some compensating security practice.
The single workflow was fully analyzed, uses read-only permissions, and has no untrusted checkout or script-injection paths. However, all four action references are unpinned and the audit found a high-confidence unpinned container image, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
phpstan/phpstan Version ^2.1 | — | — |
contempt/contracts Version self.version | — | — |
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
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.