@microsoft/fast-web-utilities
FAST web utilities
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft1es and fastsvc are Microsoft service accounts used for consolidated OSS publishing; addition is consistent with Microsoft's internal npm governance practices. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of 'microsoft' maintainer in favor of dedicated service accounts (fastsvc, microsoft1es) is consistent with Microsoft's internal publishing consolidation. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is a minor provenance gap consistent with a CI/CD environment change during Microsoft's publishing account transition; not a security signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from chrisdholt to nirice occurred in 2018 — a legitimate historical maintainer transition within the Microsoft FAST team. nirice has 1601 approved packages and no rejections. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft FAST package published before Sigstore provenance was standard on npm; no security concern given the established repo and publisher. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 1 / 26 | |
| 5.4.1 | 1 / 26 | |
| 5.4.0 | 1 / 26 | |
| 5.3.0 | 1 / 26 | |
| 5.2.0 | 1 / 26 | |
| 5.1.0 | 1 / 29 | |
| 5.0.2 | 1 / 29 | |
| 5.0.1 | 1 / 29 | |
| 5.0.0 | 1 / 31 | |
| 4.8.1 | 1 / 31 | |
| 4.8.0 | 1 / 31 | |
| 4.7.3 | 1 / 14 | |
| 4.7.2 | 1 / 14 | |
| 4.7.1 | 1 / 14 | |
| 4.7.0 | 1 / 14 | |
| 4.6.1 | 1 / 14 | |
| 4.6.0 | 1 / 14 | |
| 4.5.2 | 1 / 14 | |
| 4.5.1 | 1 / 14 | |
| 4.5.0 | 1 / 14 | |
| 4.4.5 | 1 / 15 | |
| 4.4.4 | 1 / 15 | |
| 4.4.3 | 1 / 15 | |
| 4.4.2 | 1 / 15 | |
| 4.4.1 | 1 / 16 | |
| 4.4.0 | 1 / 16 | |
| 4.3.7 | 1 / 16 | |
| 4.3.6 | 1 / 16 | |
| 4.3.5 | 1 / 16 | |
| 4.3.4 | 1 / 16 | |
| 4.3.3 | 1 / 16 | |
| 4.3.2 | 1 / 16 | |
| 4.3.1 | 1 / 16 | |
| 4.3.0 | 1 / 16 | |
| 4.2.1 | 1 / 16 | |
| 4.2.0 | 1 / 16 | |
| 4.1.0 | 1 / 16 | |
| 4.0.1 | 0 / 17 | |
| 4.0.0 | 0 / 17 | |
| 3.1.3 | 0 / 17 | |
| 3.1.2 | 0 / 17 | |
| 3.1.1 | 0 / 17 | |
| 3.1.0 | 0 / 17 | |
| 3.0.4 | 0 / 17 | |
| 3.0.3 | 0 / 16 | |
| 3.0.2 | 0 / 16 | |
| 3.0.1 | 0 / 16 | |
| 3.0.0 | 0 / 13 | |
| 2.2.0 | 0 / 13 | |
| 2.1.0 | 0 / 13 | |
| 2.0.0 | 0 / 13 |
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fastsvc.
This version was published by a different npm account than previous versions on 2021-09-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fastsvc.
This version was published by a different npm account than previous versions on 2021-05-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
2 findingsThis version was published by a different npm account than previous versions on 2021-02-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
2 findingsThis version was published by a different npm account than previous versions on 2020-06-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
2 findingsThis version was published by a different npm account than previous versions on 2020-06-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
2 findingsThis version was published by a different npm account than previous versions on 2019-10-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
2 findingsThis version was published by a different npm account than previous versions on 2019-10-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
2 findingsThis version was published by a different npm account than previous versions on 2019-08-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findingsThis version was published by a different npm account than previous versions on 2019-05-31. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2019-04-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
2 findingsThis version was published by a different npm account than previous versions on 2018-11-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2018-11-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2018-10-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-10-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2018-09-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2018-08-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.