npmpackage.info

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

@microsoft/teams-js

JavaScript library for use by Microsoft Teams apps

2.31.1

434

NOASSERTION

TypeScript

20,525,763 6.9

Installations

npm install @microsoft/teams-js

Pull Requests

Open

21

Total

1,800

Closed

377

Merged

1,402

Issues

Open

177

Total

834

Closed

657

Releases

v2.31.1

Published on 20 Nov 2024

v2.31.0

Published on 13 Nov 2024

v2.30.0

Published on 21 Oct 2024

v2.29.0

Published on 04 Oct 2024

v2.28.0

Published on 04 Sept 2024

v2.26.0

Published on 09 Aug 2024

View all 74 releases

Developer

OfficeDev

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

18.20.5

NPM Version

10.8.2 Statistics

434 Stars

2,191 Commits

198 Forks

107 Watching

319 Branches

228 Contributors

Updated on 27 Nov 2024

Languages

TypeScript (96.59%)

JavaScript (2.12%)

HTML (0.54%)

C# (0.53%)

CSS (0.2%)

PowerShell (0.02%)

Total Downloads

Cumulative downloads

Total Downloads

20,525,763

Last day

-28.5%

28,965

Compared to previous day

Last week

-1.8%

191,263

Compared to previous week

Last month

35.9%

824,605

Compared to previous month

Last year

24%

6,900,539

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

debug base64-js

Dev Dependencies

@types/debug

Versions

Microsoft Teams JavaScript client library

Welcome to the Teams client library monorepo! For breaking changes, please refer to our changelog in the <root>/packages/teams-js directory. This repository contains the core teams-js package as well as tools and applications for analyzing and testing.

Getting Started

The following guide references steps to build the entire project including TeamsJS and all of the included apps. For guidelines on just building an individual app please look at the Apps.

Building this Project

Clone this repository git clone https://github.com/OfficeDev/microsoft-teams-library-js.git
Run pnpm install from repo root
Run pnpm build from repo root
To run Unit tests, run pnpm test

Submitting a Pull Request

Please look through our Contributing Guide for important details on how to submit a pull request and contribute to this repository.

NOTE: Make sure pnpm@9.0.6 or greater is installed as a global tool, by running npm install -g pnpm@9.0.6.

TIP: whenever building or testing the Teams client library, you can run pnpm build or pnpm test from the packages/teams-js directory.

This JavaScript library is part of the Microsoft Teams developer platform. See full library reference documentation.

Packages

Contain the core exports for the repository.

teams-js

Used to integrate custom services and applications with Teams, Outlook, and Office.

Apps

The apps folder contains applications used to test various aspects of the library.

Teams Perf Test App

React application used to locally test the loading times of the library.

Teams Test App

Application used to test the functionality of the various library APIs.

SSR Test App

Application used to ensure library changes do not break server-side rendering capabilities.

Locally generating reference documentation

If you would like to locally generate reference documentation for TeamsJS v2, simply utilize the script pnpm run docs either from the monorepo root or inside the teams-js project root (packages/teams-js). This should output the generated documentation to packages/teams-js/docs.

Contributing

We strongly welcome and encourage contributions to this project. Please read the contributor's guide which contains important information.

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.

No vulnerabilities found.

10

Code-Review

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

10

Security-Policy

Determines if the project has published a security policy.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

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

10

SAST

Determines if the project uses static code analysis.

9

Binary-Artifacts

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

9

License

Determines if the project has defined a license.

8

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Token-Permissions

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

0

CII-Best-Practices

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

0

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 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/codeql.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:47: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/codeql.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:59: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/codeql.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yml:72: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/codeql.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/main.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/main.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/main.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/main.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:44: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/main.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:63: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/main.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/main.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/main.yml:84: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/main.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/postrelease.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/postrelease.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/postrelease.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/postrelease.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/postrelease.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/postrelease.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/postrelease.yml:50: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/postrelease.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/prerelease.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/prerelease.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/prerelease.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/prerelease.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/prerelease.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/prerelease.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/runtimeCheck.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/OfficeDev/microsoft-teams-library-js/runtimeCheck.yml/main?enable=pin
Warn: npmCommand not pinned by hash: .github/workflows/prerelease.yml:23
Info: 0 out of 14 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 5 third-party GitHubAction dependencies pinned
Info: 0 out of 1 npmCommand dependencies pinned

0

Fuzzing

Determines if the project uses fuzzing.

Score

6.9

/10

Last Scanned on 2024-11-25

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