npm package report

Is marked safe?

Checked against the XYZ decision brain: known-malicious corpus, advisories, commit-level findings, dependencies and provenance.

cyberxyz.io/packages/npm/marked
npm packagelast checked 2026-06-10

marked · verdict ALLOW · no known risk

0.6/10
XYZ SCORE
SUMMARY

Verdict ALLOW · 40 known dependencies · provenance: unknown

Re-check live →

SIGNALS
Advisory HistoryclearOK

19 historical advisory record(s) on this package (max severity HIGH). Add a version to check whether it is affected.

DEPENDENCIES
@arethetypeswrong/cli@^0.12.2clean
@arethetypeswrong/cli@^0.13.1clean
@arethetypeswrong/cli@^0.13.2clean
@arethetypeswrong/cli@^0.13.3clean
@arethetypeswrong/cli@^0.13.5clean
@arethetypeswrong/cli@^0.13.6clean
@arethetypeswrong/cli@^0.15.0clean
@arethetypeswrong/cli@^0.15.3clean
@arethetypeswrong/cli@^0.15.4clean
@arethetypeswrong/cli@^0.16.4clean
@arethetypeswrong/cli@^0.17.0clean
@arethetypeswrong/cli@^0.17.1clean
@arethetypeswrong/cli@^0.17.2clean
@arethetypeswrong/cli@^0.17.3clean
@arethetypeswrong/cli@^0.17.4clean
@arethetypeswrong/cli@^0.18.1clean
@babel/core@^7.10.4clean
@babel/core@^7.11.6clean
@babel/core@^7.12.10clean
@babel/core@^7.12.17clean
PACKAGE markedECOSYSTEM npmDECISION ALLOW

Baked snapshot · run a live check for the current verdict · browse all packages