mjml-button
87%
Total Score
100
100
95
80
50
No build attestation, trusted publisher identity, or staged publishing is reported, leaving publication provenance less transparent despite the package's otherwise established release history.
The repository uses Babel and npm scripts, but no security scanning tools were detected. Build tooling is present; the missing security automation is a genuine transparency and risk-management gap.
No repository security policy was found, reducing disclosure and security-maintenance transparency.
All three workflows lack top-level permissions declarations, although none declares top-level write permissions and one uses job-level permissions. Explicit least-privilege configuration would be clearer, so this remains a workflow hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
lodash Version ^4.17.21 | — | — |
mjml-core Version 5.4.1 | — | — |
@babel/runtime Version ^7.28.4 | — | — |
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.