Package Health Score

61 / 100

security
Security review needed
popularity
Limited
maintenance
Inactive
community
Active

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
5.0.1	\|	06/2023	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.2.5	\|	05/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.8.0	\|	04/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.10.0	\|	11/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.9.0	\|	11/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (239)

GitHub Stars: 460
Forks: 189
Contributors: 100

Direct Usage Popularity

The npm package ms-teams-vscode-extension receives a total of 239 downloads a week. As such, we scored ms-teams-vscode-extension popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package ms-teams-vscode-extension, we found that it has been starred 460 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 100
Funding: No

With more than 10 contributors for the ms-teams-vscode-extension repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 225
Open PR: 47
Last Release: 1 year ago
Last Commit: 12 days ago

Further analysis of the maintenance status of ms-teams-vscode-extension based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for ms-teams-vscode-extension is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 4 years
Dependencies: 33 Direct
Versions: 825
Install Size: 86.2 MB
Dist-tags: 6
# of Files: 551
Maintainers: 1
TS Typings: No

ms-teams-vscode-extension has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

Microsoft Teams Toolkit for Visual Studio Code

What is Teams Toolkit?

The Teams Toolkit helps developers create and deploy Teams apps with integrated identity, access to cloud storage, data from Microsoft Graph, and other services in Azure and Microsoft 365 with a "zero-configuration" approach to the developer experience.

TTK GIF

What are Teams app "Capabilities"?

Teams apps are a combination of capabilities and entry points. For example, people can chat with your app's bot (capability) in a channel (entry point).

Tab

Tabs are Teams-aware webpages embedded in Microsoft Teams. They are simple HTML tags that point to domains declared in the app manifest and can be added as part of a channel inside a team, group chat, or personal app for an individual user.

Bot

Bots allow users to interact with your web service through text, interactive cards, and task modules.

Message Extension

Message extensions allow users to interact with your web service through buttons and forms in the Microsoft Teams client.

Getting started

Open Teams Toolkit to create a new app and start coding!

GettingStarted

follow the Get Started instructions in our documentation to start with a new project.

In the Teams Toolkit for Visual Studio Code, you can easily discover all applicable commands in the sidebar and Command Palette with the keyword "Teams". It also supports Command Line Interface (CLI) to increase efficiency.

Prerequisites

Verify you have the right prerequisites for building Teams apps and install some recommended development tools. Read more details.

	Node.js As a fundamental runtime context for Teams app, Node.js v14.x, v16.x or v18.x is required. If you develop SPFx Tab app, please install v16.x.
	Microsoft 365 The Teams Toolkit requires a Microsoft 365 organizational account where Teams is running and has been registered.
	Azure The Teams Toolkit may require an Azure account and subscription to deploy the Azure resources for your project.

> Don’t have a Microsoft 365 account to experience building Teams app? Sign up for Microsoft Developer Program, which allows you to have a testing tenant with preconfigured permissions.

Create your project

Use the Teams Toolkit for Visual Studio Code to set up your first app project. Create your tab app project using the following steps:

Ensure you've installed the Microsoft Teams Toolkit for Visual Studio Code
Select the Teams Toolkit icon in the Visual Studio Code sidebar.
Select Create a New App button from the sidebar.
Select a capability that you want to build in your app.
Select an app template from the list of available templates.
Select JavaScript as the programming language.
Choose a location where your new application will be created in a new folder.
Type a name for your project and hit Enter.

Configure your app

At its core, the Teams app embraces three components:

The Microsoft Teams client (web, desktop or mobile) where users interact with your app.
A server that responds to requests for content that will be displayed in Teams, e.g., HTML tab content or an adaptive card.
A Teams app package consisting of three files:

✔️ The manifest.json.

✔️ A color icon for your app to display in the public or organization app catalog.

✔️ An outline icon for display on the Teams activity bar.

When an app is installed, the Teams client parses the manifest file to determine needed information like the name of your app and the URL where the services are located.

To configure your app, navigate to the appPackage/manifest.json file and edit the manifest.
The toolkit will automatically update the app registration accordingly during app side-loading and publishing.

Preview your app on your local/remote dev environment

Simply press F5 to run your first Teams app or navigate to the Debug tab in the activity bar and select the Run and Debug icon to display the Run and Debug view. By default, the toolkit will automatically help you to set up a local environment and load the app in Teams.

Run and debug

If you want to have a better estimation of how the app will behave in the cloud environment, you can deploy your resources to the cloud and preview your app with the backend running in the cloud (remote).

Deploy your application to Azure

Deployment happens in two steps: Provisioning and Deployment. Provisioning creates all the necessary Azure resources that your application uses. It is typically done once. To provision your backend to an active Azure subscription:

In the Visual Studio Code Command Palette, enter "teams" and choose the command Teams: Provision.
You will be asked to sign into your Azure account. This is the account where Azure resources will be provisioned. Typically this is different from the Microsoft 365 account you used to sign in earlier.
You will be asked to select a subscription to use from the Azure account.
Once provisioning is completed, Visual Studio Code will pop up the notification with the message "'app name' successfully provisioned in the cloud.".

Deploy copies of your application to the provisioned Azure resources. It is typically done after every change to your application. To deploy your application to the provisioned resources in an active Azure subscription:

In the Visual Studio Code Command Palette, enter "teams" and choose the command Teams: Deploy.
Select Tab app and Backend to deploy.
Once deployment is finished, go to the Visual Studio Code Debug Panel (Ctrl+Shift+D / ⌘⇧-D or View -> Run) and select Launch Remote (Edge).
Press the start button (green arrow) to launch your app - now running remotely on Azure!

Read more on provision and deployment to Azure.

Publish your application to Teams

When your application resources and infrastructure are deployed successfully, you can publish and register your app to the Teams app catalog to share with others in your organization.

In the Visual Studio Code Command Palette, enter "teams" and choose the command Teams: Publish.
Depending on your permission, you can send your app to the admin portal directly, or manually submit the app package file to your admin to check.
Once your app is approved by your admin, you can see it under the Built for your org section in the Teams app store.

Explore Code Samples

Explore our samples to help you quickly get started with the basic Teams app concepts and code structures.

Contributing

There are many ways in which you can participate in the project, for example:

Download our latest builds.
Submit bugs and feature requests, and help us verify as they are checked in
Review source code changes
Review the documentation and make pull requests for anything from typos to new content

Reporting security issues

Give security researchers information on how to privately report security vulnerabilities found in your open-source project. See more details Reporting security issues.

Telemetry

The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft's privacy statement. Our privacy statement is located at Microsoft Privacy Statement. You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices.

Telemetry Configuration

Telemetry collection is on by default. To opt out, please set the telemetry.enableTelemetry setting to false. Learn more in our FAQ.

Code of conduct

See Microsoft Open Source code of conduct.

Trademark

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

License

Licensed under the MIT license.

ms-teams-vscode-extension development dependencies

@azure/arm-subscriptions @azure/eslint-plugin-azure-sdk @azure/identity-vscode @commitlint/cli @commitlint/config-conventional @fluentui/react @istanbuljs/nyc-config-typescript @microsoft/eslint-plugin-teamsfx @types/adm-zip @types/chai @types/chai-as-promised @types/chai-spies @types/detect-port @types/express @types/fs-extra @types/glob @types/jscodeshift @types/keytar @types/lodash @types/mocha @types/node @types/react @types/react-copy-to-clipboard @types/react-dom @types/react-router-dom @types/react-syntax-highlighter @types/sinon @types/tmp @types/underscore @types/uuid @types/validator @types/vscode @typescript-eslint/eslint-plugin @typescript-eslint/parser @vscode/codicons @vscode/vsce adm-zip chai chai-as-promised chai-spies copy-webpack-plugin copyfiles css-loader detect-port eslint eslint-plugin-import eslint-plugin-no-secrets eslint-plugin-prettier find-process fs-extra glob html-webpack-plugin kill-port-process lint-staged mocha mocha-junit-reporter mocha-multi-reporters mock-require ms-rest node-loader nyc prettier react react-dom react-intl react-router-dom reflect-metadata rimraf sass sass-loader sinon source-map-support style-loader svgtofont terser-webpack-plugin tmp ts-loader ts-node ts-sinon ttypescript typemoq typescript umd-compat-loader url-loader uuid verdaccio webpack webpack-cli winston

FAQs

What is ms-teams-vscode-extension?

Create, debug, and deploy Teams apps with Teams Toolkit. Visit Snyk Advisor to see a full health score report for ms-teams-vscode-extension, including popularity, security, maintenance & community analysis.

Is ms-teams-vscode-extension popular?

The npm package ms-teams-vscode-extension receives a total of 239 weekly downloads. As such, ms-teams-vscode-extension popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is ms-teams-vscode-extension well maintained?

We found indications that ms-teams-vscode-extension is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is ms-teams-vscode-extension safe to use?

While scanning the latest version of ms-teams-vscode-extension, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 16 November-2024, at 23:05 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (239)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

Microsoft Teams Toolkit for Visual Studio Code

What is Teams Toolkit?

What are Teams app "Capabilities"?

Tab

Bot

Message Extension

Getting started

Prerequisites

Node.js

Microsoft 365

Azure

Create your project

Configure your app

Preview your app on your local/remote dev environment

Deploy your application to Azure

Publish your application to Teams

Explore Code Samples

Contributing

Reporting security issues

Telemetry

Telemetry Configuration

Code of conduct

Trademark

License

ms-teams-vscode-extension dependencies

ms-teams-vscode-extension development dependencies

FAQs

What is ms-teams-vscode-extension?

Is ms-teams-vscode-extension popular?

Is ms-teams-vscode-extension well maintained?

Is ms-teams-vscode-extension safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues