npm JavaScript not analyzable deep scan unknown

@hasna/connectors

v1.4.5
npm

not analyzable — repository too large to scan in full (large monorepo)

Open source connector library - Install API connectors with a single command

maintainer
andreihasna2
licence
Apache-2.0
first seen
2026-07-02
last seen
2026-09-17
releases · 30d
4
short id
risk insufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

risk trajectory 2 movements
  • A · 3 A · 0
  • B · 18 A · 3
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

other grade factors evidence elsewhere
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@hasna/connectors/badge.svg)](https://mcpobservatory.com/servers/npm:@hasna/connectors/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 andreihasna2.