innis/nostr-nip46
Clear documentation, tests, and a lean runtime dependency set reduce adoption friction. The automated workflow audit found no dangerous patterns, though its action references are not pinned.
72%
Total Score
67
86
67
Health Score Breakdown
The repository is owned by an individual user rather than an organization, so the single-contributor maintenance concentration is not offset by visible organizational backing.
One contributor made all 10 commits in the last 3 months, creating a meaningful continuity risk if that maintainer becomes unavailable. The repository is actively maintained, which limits the immediate abandonment concern but does not remove the concentration.
Composer build tooling is present, but no security scanning tools were detected. For a cryptographic remote-signer library, that is a modest transparency and maintenance gap.
The repository has no security policy. For software handling signing and encrypted remote-signer flows, the lack of a documented reporting path reduces security-maintenance transparency.
Version v0.4.0 is not a stable major release, so its API may still change. It is not marked as a prerelease, which partly offsets that concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 John Innis |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 innis/nostr-core Version ^0.8.1 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 2 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.