npm analyzed 0.43.1

task-master-ai

v0.43.1
npm

A task management system for ambitious AI-driven development that doesn't overwhelm and confuse Cursor.

maintainer
crunchyman-ralph
license
MIT WITH Commons-Clause
first seen
2026-05-22
last seen
2026-06-17
releases · 30d
0
short id
risk 34/100 · heuristic grade
B low
  • capability exposureinferred+35
  • inherited (deps)attested+1
  • tool safetyinferred+12
  • trust mitigatorsmixed−14

attestedinferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 9m ago · see ecosystem CVEs →

risk trajectory 2 movements
  • B · 22B · 34
  • B · 34B · 22
capability exposure grade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

inherited (deps) · grade factor +1

inherited via dependencies 1
LOW
Vercel’s AI SDK's filetype whitelists can be bypassed when uploading files via ai · 1 hop CVE-2025-48985 fixed in 5.0.52
tool safety 1 findings · grade factor +12
  1. highdangerous code

    credential logged in 1 file(s)

skills & danger signals npm-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed v0.43.1 · analyzer v18 · 8h ago

skills & prompt files 3

danger signals1

  • credential in logscredential in logpackage/dist/dependency-manager-BJq6jWA5.js:87Context:`)),t.orgName&&console.log(B.gray(` Organization: ${t.orgName}`)),t.briefName&&console.log(B.gray(` Brief: ${t.briefName}`))),{success:!0,action:`status`,credentials:{token:e?.access_tok
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:task-master-ai/badge.svg)](https://mcpobservatory.com/servers/npm:task-master-ai/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of crunchyman-ralph.