@microsoft/teamsfx-api MIT 34 versions

@microsoft/teamsfx-api

npm Repository

teamsfx framework api

34

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

microsoft1esmicrosoft-oss-releaseszhyuernintanmsteamsfx

Keywords

teamsfxapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:@shared/eslint-config	AI (npm-metadata): Monorepo-relative devDependency, not an external URL risk.	ai	2026/07/25
npm-metadata	url-dep:@shared/prettier-config	AI (npm-metadata): Monorepo-relative devDependency, not an external URL risk.	ai	2026/07/25
phantom-deps	phantom-dep:@types/fs-extra	AI (phantom-deps): Type-only package, used by convention.	ai	2026/07/25
phantom-deps	phantom-dep:chai	AI (phantom-deps): Used in test config, not a security concern.	ai	2026/07/11
dependencies	unvetted-dep:@microsoft/teams-manifest	AI (dependencies): First-party Microsoft package within same org/monorepo.	ai	2026/07/11
phantom-deps	phantom-dep:axios	AI (phantom-deps): Config-referenced, common HTTP lib, no risk.	ai	2026/07/11
phantom-deps	phantom-dep:jsonschema	AI (phantom-deps): Config-referenced utility dep, no risk.	ai	2026/07/11

Versions (showing 34 of 34)

Version	Deps	Published
0.24.0	6 / 33	2026-03-30
0.23.15	6 / 33	2026-07-14
0.23.14	6 / 33	2026-05-20
0.23.13	6 / 33	2026-04-17
0.23.12	6 / 32	2026-03-11
0.23.11	6 / 32	2025-11-13
0.23.10	6 / 32	2025-09-28
0.23.9	6 / 32	2025-09-18
0.23.8	6 / 32	2025-07-22
0.23.7	6 / 32	2025-06-03
0.23.6	6 / 32	2025-05-19
0.23.4	6 / 32	2024-12-18
0.23.3	6 / 32	2024-11-19
0.23.2	6 / 32	2024-10-17
0.23.1	7 / 32	2024-05-29
0.23.0	7 / 32	2024-05-15
0.17.2	8 / 28	2022-04-07
0.15.0	7 / 30	2022-02-22
0.14.0	7 / 30	2022-02-09
0.13.0	7 / 29	2022-01-10
0.12.0	7 / 29	2021-12-16
0.11.0	7 / 29	2021-11-30
0.10.0	7 / 29	2021-11-02
0.9.0	7 / 28	2021-10-19
0.8.0	7 / 26	2021-09-22
0.7.0	7 / 26	2021-09-08
0.6.0	7 / 24	2021-08-23
0.5.0	7 / 24	2021-08-10
0.4.0	7 / 24	2021-07-26
0.3.0	7 / 22	2021-07-12
0.2.1	7 / 21	2021-06-29
0.2.0	7 / 19	2021-06-15
0.1.1	7 / 19	2021-05-22
0.1.0	7 / 19	2021-05-21

v0.23.15

1 finding

LOW No provenance attestation provenance

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

v0.23.12

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: msteamsfx → nintan (on 2026-03-11, known maintainer) provenance

This version was published by a different npm account (nintan) than the most recent previously approved version (msteamsfx) on 2026-03-11, but nintan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.23.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.

v0.23.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.

v0.23.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.

v0.23.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.

v0.23.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.

v0.17.2

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.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.

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.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.