mjml-core
88%
Total Score
100
100
94
80
50
No build attestation, trusted publisher identity, or staged publishing is reported, leaving publication provenance less transparent than ideal.
The repository uses build tooling through Babel and npm scripts, but no security-scanning tools are reported, leaving a security-hygiene gap.
No repository security policy is present, reducing transparency around vulnerability reporting and response expectations.
All three workflows lack top-level token permissions declarations, and none declares read-only permissions; although no workflow has top-level write permissions, explicit least-privilege configuration would be safer.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
juice Version ^11.1.1 | — | — |
lodash Version ^4.17.21 | — | — |
cheerio Version ^1.2.0 | — | — |
cssnano Version ^7.1.9 | — | — |
postcss Version ^8.5.28 | — | — |
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.