SkillTotal

Is @microsoft/teams.api safe?

No malicious indicators - review capabilities before installing
Notable — review in context (capabilities are not malware):
  • Node.js network egress
  • Delegated authentication (OAuth 2.0 / OIDC)

@microsoft/teams.api is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 2 risky constructs are reported for review. It can: delegated authentication and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

@microsoft/teams.api 2.1.0

npm_package · npm:@microsoft/teams.api
LOW
0
/ 100 risk score
Snapshot · scanned Sep 25, 2026 · @microsoft/teams.api@2.1.0 · engine 0.53.0 / ruleset 60

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of @microsoft/teams.api's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
delegated authenticationnetwork egress

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Network egress
Interaction & Communication / Direct Communication
Delegated authentication
Tool Execution Context / User Delegated Credentials

Findings (2)

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

import { AxiosResponse } from 'axios';
const res = await this.http.get(
const res = await this.http.get(
const res = await this.http.get(
const res = await this.http.get(
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(
const res = await this.http.get(
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url, { params });
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url, { params });
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(url);
const res = await this.http.get(
const res = await this.http.get(

Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.

Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.

LOWDelegated authentication (OAuth 2.0 / OIDC)ST-AUTH-DELEGATED

An OAuth 2.0 / OpenID Connect delegated-authentication flow was detected (authorization-code / refresh-token / token-exchange grant, an OIDC authorize/discovery endpoint or id_token, or a delegation library). Tools authenticate with the end user's delegated, scoped credentials rather than a long-lived embedded service credential. (3 occurrence(s) shown as evidence).

* sourced from trusted identity infrastructure (MSAL, Bot Framework API
* sourced from trusted identity infrastructure (MSAL, Bot Framework API
* sourced from trusted identity infrastructure (MSAL, Bot Framework API

Fix: Delegated auth is a lower-blast-radius execution context than an embedded static credential. Confirm the requested scopes are minimal and that tokens are never logged or forwarded off-host.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →