npmpackage.info

Gathering detailed insights and metrics for @microsoft/teams-connector

Other packages similar to @microsoft/teams-connector

@fusebit/msteams-connector

2.4.1

Fusebit Connector for Microsoft Teams

project-coriander-test-package-ms-teams

1.0.2

A Coveo Connector for Microsoft Teams

winston-office365-connector-hook

0.1.7

A Winston transport hook to send logs over to a Office 365 Connector, e.g. Microsoft Teams channel.

@azure/connectors-microsoftteams

0.0.1-alpha

MicrosoftTeamsConnector Library with typescript type definitions for node.js and browser.

Gathering detailed insights and metrics for @microsoft/teams-connector

@microsoft/teams-connector - 0.1.0-preview.1 | npmpackage.info

@microsoft/teams-connector

SDK focused on building AI based applications and extensions for Microsoft Teams and other Bot Framework channels

0.1.0-preview.1

596

MIT

1.56 MB

7.6

Installations

npm install @microsoft/teams-connector

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

18.16.0

NPM Version

9.5.1 Pull Requests

Open

10

Total

1,379

Closed

221

Merged

1,148

Issues

Open

136

Total

1,082

Closed

946

Releases

py-1.8.1

Updated on Jul 01, 2025

dotnet-1.11.0

Updated on May 27, 2025

dotnet-1.10.1

Updated on May 03, 2025

dotnet-1.9.1

Updated on May 03, 2025

py-1.8.0

Updated on Apr 01, 2025

py-1.7.0

Updated on Mar 06, 2025

View All 43 releases

Languages

TypeScript

Python

Bicep

HTML

JavaScript

Shell

C# (38.94%)

TypeScript (33.11%)

Python (22.11%)

Bicep (4.8%)

HTML (0.92%)

JavaScript (0.08%)

Shell (0.04%)

Developer

microsoft

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

596 Stars

1,221 Commits

243 Forks

45 Watchers

30 Branches

133 Contributors

Updated on Jul 15, 2025

Maintainers

View All 133 Contributors

Package Meta Information

Latest Version

0.1.0-preview.1

Package Id

@microsoft/teams-connector@0.1.0-preview.1

Unpacked Size

1.56 MB

Size

228.15 kB

File Count

419

NPM Version

9.5.1

Node Version

18.16.0

Published on

Aug 08, 2023

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@azure/identity @azure/ms-rest-js adal-node axios base64url cross-fetch jsonwebtoken rsa-pem-from-mod-exp uuid zod

Dev Dependencies

@types/jsonwebtoken @types/node @types/uuid dotenv nock should

Microsoft Bot Framework Connector for Node.js

Within the Bot Framework, the Bot Connector service enables your bot to exchange messages with users on channels that are configured in the Bot Framework Portal.

Requirement

Node.js version: 6.x.x or higher

How to Install

1npm install botframework-connector

How to Use

Authentication

Your bot communicates with the Bot Connector service using HTTP over a secured channel (SSL/TLS). When your bot sends a request to the Connector service, it must include information that the Connector service can use to verify its identity.

To authenticate the requests, you'll need configure the Connector with the App ID and password that you obtained for your bot during registration and the Connector will handle the rest.

More information: https://docs.microsoft.com/en-us/bot-framework/rest-api/bot-framework-rest-connector-authentication

Example

Client creation (with authentication), conversation initialization and activity send to user.

1var { ConnectorClient, MicrosoftAppCredentials } = require('botframework-connector');
2
3async function connectToSlack() {
4    var credentials = new MicrosoftAppCredentials('<your-app-id>', '<your-app-password>');
5
6    var botId = '<bot-id>';
7    var recipientId = '<user-id>';
8
9    var client = new ConnectorClient(credentials, { baseUri: 'https://slack.botframework.com' });
10
11    var conversationResponse = await client.conversations.createConversation({
12        bot: { id: botId },
13        members: [
14            { id: recipientId }
15        ],
16        isGroup: false
17    });
18
19    var activityResponse = await client.conversations.sendToConversation(conversationResponse.id, {
20        type: 'message',
21        from: { id: botId },
22        recipient: { id: recipientId },
23        text: 'This a message from Bot Connector Client (NodeJS)'
24    });
25
26    console.log('Sent reply with ActivityId:', activityResponse.id);
27}

Simple EchoBot Example (source code)

EchoBot is a minimal bot that receives message activities and replies with the same content. The sample shows how to use restify/express for listening to activities and the ConnectorClient for sending activities.

Rest API Documentation

For the Connector Service API Documentation, please see our API reference.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

License

Licensed under the MIT License.

No vulnerabilities found.

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

Dependency-Update-Tool

Determines if the project uses a dependency update tool.

10

Maintained

Determines if the project is "actively maintained".

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

Reason

GitHub workflow tokens follow principle of least privilege

Details

Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/coverage.yml:21
Info: jobLevel 'contents' permission set to 'read': .github/workflows/coverage.yml:50
Info: jobLevel 'contents' permission set to 'read': .github/workflows/coverage.yml:83
Info: jobLevel 'contents' permission set to 'read': .github/workflows/coverage.yml:124
Info: jobLevel 'contents' permission set to 'read': .github/workflows/dotnet-build-test-lint.yml:34
Info: jobLevel 'actions' permission set to 'read': .github/workflows/dotnet-codeql.yml:33
Info: jobLevel 'contents' permission set to 'read': .github/workflows/dotnet-codeql.yml:34
Info: jobLevel permissions set to 'read-all': .github/workflows/dotnet-publish.yml:19
Info: jobLevel 'contents' permission set to 'read': .github/workflows/dotnet-publish.yml:33
Info: jobLevel 'contents' permission set to 'read': .github/workflows/js-build-test-lint.yml:28
Info: jobLevel 'actions' permission set to 'read': .github/workflows/js-codeql.yml:32
Info: jobLevel 'contents' permission set to 'read': .github/workflows/js-codeql.yml:33
Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/pr-style.yml:14
Info: jobLevel 'contents' permission set to 'read': .github/workflows/python-build-test-lint.yml:29
Info: jobLevel 'actions' permission set to 'read': .github/workflows/python-codeql.yml:32
Info: jobLevel 'contents' permission set to 'read': .github/workflows/python-codeql.yml:33
Info: jobLevel 'contents' permission set to 'read': .github/workflows/scorecards.yml:29
Info: jobLevel 'actions' permission set to 'read': .github/workflows/scorecards.yml:30
Info: topLevel permissions set to 'read-all': .github/workflows/coverage.yml:13
Info: topLevel 'contents' permission set to 'read': .github/workflows/dependency-review.yml:13
Info: topLevel permissions set to 'read-all': .github/workflows/dotnet-build-test-lint.yml:17
Info: topLevel 'contents' permission set to 'read': .github/workflows/dotnet-codeql.yml:26
Info: topLevel permissions set to 'read-all': .github/workflows/dotnet-publish.yml:13
Info: topLevel permissions set to 'read-all': .github/workflows/js-build-test-lint.yml:14
Info: topLevel 'contents' permission set to 'read': .github/workflows/js-codeql.yml:25
Info: topLevel permissions set to 'read-all': .github/workflows/pr-style.yml:7
Info: topLevel permissions set to 'read-all': .github/workflows/python-build-test-lint.yml:16
Info: topLevel 'contents' permission set to 'read': .github/workflows/python-codeql.yml:25
Info: topLevel permissions set to 'read-all': .github/workflows/scorecards.yml:18
Info: no jobLevel write permissions found

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

10

CI-Tests

Determines if the project runs tests before pull requests are merged.

10

Contributors

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

9

SAST

Determines if the project uses static code analysis.

5

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 5

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/coverage.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/microsoft/teams-ai/coverage.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/coverage.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/microsoft/teams-ai/coverage.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/coverage.yml:65: update your workflow using https://app.stepsecurity.io/secureworkflow/microsoft/teams-ai/coverage.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/coverage.yml:103: update your workflow using https://app.stepsecurity.io/secureworkflow/microsoft/teams-ai/coverage.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/coverage.yml:143: update your workflow using https://app.stepsecurity.io/secureworkflow/microsoft/teams-ai/coverage.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/coverage.yml:156: update your workflow using https://app.stepsecurity.io/secureworkflow/microsoft/teams-ai/coverage.yml/main?enable=pin
Warn: pipCommand not pinned by hash: .github/workflows/coverage.yml:136
Warn: pipCommand not pinned by hash: .github/workflows/coverage.yml:137
Warn: nugetCommand not pinned by hash: .github/workflows/dotnet-build-test-lint.yml:44: pin your dependecies by either enabling central package management (https://learn.microsoft.com/nuget/consume-packages/Central-Package-Management) or using a lockfile (https://learn.microsoft.com/nuget/consume-packages/package-references-in-project-files#locking-dependencies)
Warn: pipCommand not pinned by hash: .github/workflows/python-build-test-lint.yml:38
Warn: pipCommand not pinned by hash: .github/workflows/python-build-test-lint.yml:39
Info: 32 out of 33 GitHub-owned GitHubAction dependencies pinned
Info: 7 out of 12 third-party GitHubAction dependencies pinned
Info: 0 out of 4 pipCommand dependencies pinned
Info: 0 out of 1 nugetCommand dependencies pinned

2

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

2

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Fuzzing

Determines if the project uses fuzzing.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

7.6

/10

Last Scanned on 2025-07-15T16:04:57Z

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More