strike extension for tiptap
88%
Total Score
healthy
Healthy: active maintenance and stable releases outweigh unpinned workflow actions and the package-to-repository naming gap.
Four of six publishing accounts use the organization's tiptap.dev domain, while _bdbch (bdbch.com) and svenadlung (ueber.io) are outside-domain accounts; organization backing limits the maintenance concern, but account hygiene is imperfect.
The repository name does not match the package name and its README does not mention @tiptap/extension-strike, so the package-to-source relationship is less transparent; the monorepo context partly explains the name mismatch but not the missing README mention.
All 19 analyzed action references are unpinned, which weakens build reproducibility; the high-confidence template-injection and low-confidence adhoc-package findings are workflow hygiene concerns, but no untrusted trigger or script-injection sink was observed.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.