← Home

@microsoft/teams.cli

npm Repository Homepage

<p> <a href="https://www.npmjs.com/package/@microsoft/teams.cli" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.cli/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.cli?activeTab=code" t

13
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

microsoft1esmicrosoft-oss-releasescorinagumaaceboaamirjawaid

Keywords

teamscliscaffolding

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): Major version rewrite of a CLI tool; 170 new files consistent with v3 feature expansion, not injected code. ai
publish-pattern new-deps-added AI (publish-pattern): All 13 new deps are established, reputable packages (Azure MSAL, commander, ajv, etc.) consistent with CLI feature expansion. ai
source-diff source-size-tripled AI (source-diff): v2→v3 major rewrite with 13 new deps and significant new functionality explains 5x size growth. ai
publish-pattern rapid-publish AI (publish-pattern): Microsoft monorepo automated releases routinely publish multiple packages in quick succession; stable pattern for this publisher. ai
provenance missing-githead AI (provenance): Trusted Microsoft publisher; missing gitHead is a CI/CD hygiene issue, not a security risk for this package. ai
dependencies unvetted-dep:handlebars AI (dependencies): Handlebars is a well-known templating library; its use in a CLI scaffolding tool is expected and appropriate. ai
dependencies unvetted-dep:@microsoft/teams.common AI (dependencies): Sibling package from the same Microsoft monorepo, pinned to the same version. No security concern. ai

Versions (showing 13 of 13)

Version Deps Published
3.0.0 16 / 5
2.0.11 6 / 9
2.0.10 6 / 9
2.0.9 6 / 9
2.0.8 6 / 9
2.0.7 6 / 9
2.0.6 6 / 9
2.0.5 6 / 9
2.0.4 6 / 9
2.0.3 6 / 9
2.0.2 6 / 9
2.0.1 6 / 9
2.0.0 6 / 9

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.11

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.10

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.9

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.