webchemistry/strict-object
The package has no license information and provides almost no consumer documentation or project scaffolding. Its small, organization-backed repository is coherent, but the long absence of releases leaves maintenance uncertain.
42%
Total Score
100
58
67
Health Score Breakdown
No declared license, license file, or repository license file was detected. That creates a significant adoption and redistribution risk for an open-source dependency.
Only two releases were published, with the latest in July 2018 and none in the last 12 months. This long period without a release materially raises abandonment and compatibility risk.
The package and repository each contain only three files, including a single source file and composer metadata. This may fit a very small library, but it provides little evidence of testing, documentation, or release engineering.
The artifact has no README, tests, or changelog, while the repository also has no tests or changelog. Missing tests and changelog are normal packaging gaps, but the absent README weakens consumer transparency for a library.
No security policy was found in the repository. This is a transparency gap, though the tiny and inactive project provides limited evidence that a formal policy is maintained.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 kdyby/strict-objects Version dev-master | — | — |
Weekly Downloads
Info
- Last Published
- 8 years 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.