securetrading/log
Stable versioning, tests, and organizational ownership make the package reasonably mature. No commits in the last three months and a weak package-to-repository naming link reduce transparency.
68%
Total Score
75
100
79
75
Health Score Breakdown
The package has existed for nearly 10 years and released version 4.0.2 recently, but only six releases overall with a median interval of about 812 days indicate a sparse cadence.
The repository recorded zero commits and zero active maintainers in the last three months, a concrete sign of currently limited maintenance activity despite the recent package release.
The repository name does not match the package name, and its README does not mention the package, making the relationship between this artifact and its source less transparent.
Composer is used for builds, but no security-scanning tool is present, leaving automated security coverage limited.
The repository has no security policy, leaving vulnerability-reporting expectations unclear; this is a hygiene gap rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^3.0 | — | — |
securetrading/ioc Version ^3.0 | — | — |
securetrading/loader Version ^2.0 | — | — |
securetrading/exception Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 months ago
- Created
- 9 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.