@azure/functions MIT 36 versions

@azure/functions

npm Repository Homepage

Microsoft Azure Functions NodeJS Framework

36

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

pgopapaulbatumfacavalcanteahmelsayedmahoegeranatolibgaaguiarvictoriahallmicrosoft-oss-releasesazure-sdkswapnilnagarmicrosoft1es

Keywords

azureazure-functionsserverlesstypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	large-new-source-files	AI (source-diff): New files are webpack bundles and source maps for the official Azure Functions library; no injected or suspicious code.	ai	2026/04/23
source-diff	source-size-tripled	AI (source-diff): Size increase reflects legitimate architectural shift to webpack bundling; consistent with official Microsoft Azure Functions library evolution.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Maintainer removal alongside additions is consistent with team rotation within Microsoft.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): @azure scope is controlled by Microsoft; publisher rotation within the org is expected team management.	ai	2026/04/23
phantom-deps	phantom-dep:long	AI (phantom-deps): long is a declared dependency used in bundled output (webpack); phantom-dep is a false positive for bundled packages.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): Maintainer additions within Microsoft's @azure scope reflect normal team changes.	ai	2026/04/23
semgrep	semgrep:base64-decode	AI (semgrep): Decoding x-ms-client-principal header is standard Azure App Service auth behavior; not a malicious payload pattern.	ai	2026/04/21

Versions (showing 36 of 36)

Version	Deps	Published
4.16.0	2 / 39	2026-05-21
4.15.0	2 / 39	2026-05-19
4.14.0	2 / 39	2026-04-23
4.13.0	2 / 39	2026-04-20
4.12.0	2 / 39	2026-03-24
4.11.2	2 / 39	2026-02-06
4.11.1	2 / 39	2026-02-03
4.11.0	3 / 38	2026-01-08
4.10.0	4 / 38	2025-12-01
4.9.0	4 / 38	2025-11-05
4.8.2	3 / 36	2025-11-05
4.8.1	3 / 36	2025-11-04
4.8.0	3 / 36	2025-09-09
4.7.3	3 / 36	2025-06-09
4.7.2	3 / 36	2025-05-22
4.7.0	3 / 36	2025-03-06
4.6.1	3 / 36	2025-02-03
4.6.0	3 / 36	2024-10-29
4.5.1	3 / 36	2024-08-28
4.5.0	3 / 36	2024-05-16
4.4.0	3 / 36	2024-04-01
4.3.0	3 / 36	2024-02-28
4.2.0	2 / 35	2024-01-30
4.1.0	2 / 35	2023-11-13
4.0.1	2 / 33	2023-09-28
4.0.0	2 / 33	2023-09-26
3.5.1	3 / 37	2023-03-27
3.5.0	3 / 37	2022-12-05
3.2.0	0 / 0	2022-05-23
3.1.0	0 / 0	2022-05-23
3.0.0	0 / 0	2021-11-23
2.0.0	0 / 0	2021-11-11
1.2.3	0 / 0	2021-01-26
1.2.2	0 / 0	2020-05-29
1.2.0	0 / 0	2020-02-14
1.0.3	0 / 0	2019-04-26

v4.16.0

1 finding

LOW No provenance attestation provenance

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

v4.15.0

1 finding

LOW No provenance attestation provenance

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

v4.14.0

1 finding

LOW No provenance attestation provenance

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

v4.12.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.

v4.11.2

1 finding

LOW No provenance attestation provenance

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

v4.11.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.

v4.11.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.

v4.10.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.

v4.9.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.

v4.8.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.

v4.8.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.

v4.8.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.

v4.7.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.

v4.7.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.

v4.7.0

2 findings

HIGH Publisher changed: erijiz → victoriahall (on 2025-03-06) provenance

This version was published by a different npm account than previous versions on 2025-03-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v4.6.1

2 findings

HIGH Publisher changed: erijiz → victoriahall (on 2025-02-03) provenance

This version was published by a different npm account than previous versions on 2025-02-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v4.6.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.

v4.5.1

1 finding

LOW No provenance attestation provenance

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

v4.5.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.

v4.4.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.

v4.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.

v4.2.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.

v4.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.

v4.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.

v4.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.

v3.5.1

1 finding

LOW No provenance attestation provenance

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

v3.5.0

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.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.

v2.0.0

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: mahoeger → erijiz (on 2021-11-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-11. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.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.

v1.2.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.

v1.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.