nostriphant/blossom
Clear licensing, tests, and a matching source repository make the package easy to inspect. The small contributor base and missing security policy warrant checking future maintenance before pinning it.
68%
Total Score
67
100
88
75
Health Score Breakdown
All 3-month commit activity came from one contributor, leaving maintenance highly concentrated even though the repository is organization-owned.
Only 2 commits were recorded in the last 3 months, despite frequent registry releases; this suggests limited recent source activity and warrants caution.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest quality and security-process gap.
The repository has no security policy, so vulnerability reporting and response expectations are not documented.
Version 0.7.6 is not a stable-major release, so compatibility expectations are lower than for a 1.x package, although it is not marked prerelease.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Rik Meijer |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nostriphant/http Version ^0.1.1 | — | — |
nostriphant/nip-01 Version ^2.2 | — | — |
nostriphant/functional Version ^2.3 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 7 months 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.