kdyby/strict-objects
The repository has no security policy or automated security scanning, leaving transparency and oversight weaker than ideal. A BSD-3-Clause license, documented tests, release notes, stable version, and organization backing provide useful evidence for a small library.
61%
Total Score
75
100
86
50
Health Score Breakdown
The latest registry release was in December 2020, with no releases in the previous 12 months and only four releases over roughly 10 years. This materially raises maintenance and compatibility risk.
There were no commits and no active maintainers in the last three months. Combined with the absence of recent registry releases, this suggests limited current maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. The build setup is positive, while the missing scanning layer modestly lowers assurance.
The repository has no security policy, so its process for receiving and disclosing vulnerabilities is unclear. This is a real transparency gap, though it does not by itself indicate abandonment.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Filip Procházka |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 10 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.