Security Trust Report: @m4l/core

@m4l/[email protected]: 55/100 | Grade: C+ | Tier: STANDARD (confidence: ±3)

Scanned on 2026-04-07 from 8 security databases. View package on npm →

TL;DR

• Package name "@m4l/core" is 1 edit(s) from popular "cors"
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  ███████████████░░░░░ 74/100
Package Health:    ████████████████░░░░ 78/100
Supply Chain:      ███░░░░░░░░░░░░░░░░░ 14/100
Community:         ████████░░░░░░░░░░░░ 40/100

Why this score?

• Supply Chain is 14 because: risky dependencies
• Community is 40 because: no public GitHub repo linked (may be private or on another platform)

Vulnerabilities

✅ No known vulnerabilities detected across 8 security databases.

Key Risk Flags

• 🔴 CRITICAL: Package name "@m4l/core" is 1 edit(s) from popular "cors"
• 🟠 HIGH: Maintainer(s) removed in v1.0.0: made4labs (evidence)
• 🟠 HIGH: Burst publishing detected — 5+ versions in a single day
• 🟠 HIGH: No license declared
• 🟠 HIGH: Depends on historically compromised package: axios

🛠️ What Should You Do?

Immediate:

Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/@m4l/core

Maintainers (1)

• made4labs ✅ 2FA (org email) — Trust profile

Methodology: 18+ signals across 4 categories (Maintainer 35%, Package 25%, Supply Chain 25%, Community 15%). Full scoring docs →

Check your project: npm i -g @cyberhub/pkgtrust && pkgtrust scan @m4l/core — CLI docs Data Sources: GitHub Advisories · OSV.dev · npm audit · Snyk · Socket.dev · npms.io · Bundlephobia · deps.dev

Report by pkgtrust · Dashboard · Compare · CLI

This is an automated security report. Not affiliated with the @m4l/core team. Updated 2026-04-07.