@fluidframework/azure-service-utils
Helper service-side utilities for connecting to Azure Fluid Relay service
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Large Microsoft OSS monorepo; provenance not yet configured but package is well-established and trustworthy. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 2.112.0 | 3 / 16 | |
| 2.111.0 | 3 / 16 | |
| 2.110.0 | 3 / 16 | |
| 2.103.0 | 3 / 16 | |
| 2.102.0 | 3 / 16 | |
| 2.101.1 | 3 / 16 | |
| 2.101.0 | 3 / 16 | |
| 2.100.1 | 3 / 16 | |
| 2.100.0 | 3 / 16 | |
| 2.93.0 | 3 / 16 | |
| 2.92.0 | 3 / 16 | |
| 2.91.0 | 3 / 16 | |
| 2.90.0 | 3 / 16 | |
| 2.83.0 | 3 / 16 | |
| 2.82.0 | 3 / 16 | |
| 2.81.1 | 3 / 16 | |
| 2.81.0 | 3 / 16 | |
| 2.80.0 | 3 / 16 | |
| 2.74.0 | 3 / 16 | |
| 2.73.0 | 3 / 15 | |
| 2.72.0 | 3 / 15 | |
| 2.71.0 | 3 / 15 | |
| 2.70.0 | 3 / 15 | |
| 2.63.0 | 3 / 15 | |
| 2.62.0 | 3 / 15 | |
| 2.61.0 | 3 / 15 | |
| 2.60.0 | 3 / 15 | |
| 2.53.1 | 3 / 15 | |
| 2.53.0 | 3 / 15 | |
| 2.52.0 | 3 / 15 | |
| 2.51.0 | 3 / 15 | |
| 2.50.0 | 3 / 16 | |
| 2.43.0 | 3 / 16 | |
| 2.42.0 | 3 / 16 | |
| 2.41.0 | 3 / 16 | |
| 2.40.0 | 3 / 16 | |
| 2.33.2 | 3 / 16 | |
| 2.33.1 | 3 / 16 | |
| 2.33.0 | 3 / 16 | |
| 2.32.0 | 3 / 16 | |
| 2.31.1 | 3 / 16 | |
| 2.31.0 | 3 / 16 | |
| 2.30.0 | 3 / 17 | |
| 2.23.0 | 3 / 17 | |
| 2.22.1 | 3 / 17 | |
| 2.22.0 | 3 / 17 | |
| 2.21.0 | 3 / 17 | |
| 2.20.0 | 3 / 17 | |
| 2.13.0 | 3 / 17 | |
| 2.12.0 | 3 / 17 | |
| 2.11.0 | 3 / 17 | |
| 2.10.0 | 3 / 17 | |
| 2.5.0 | 3 / 17 | |
| 2.4.0 | 3 / 17 | |
| 2.3.1 | 3 / 17 | |
| 2.3.0 | 3 / 17 | |
| 2.2.2 | 3 / 17 | |
| 2.2.1 | 3 / 17 | |
| 2.2.0 | 3 / 17 | |
| 2.1.2 | 3 / 17 | |
| 2.1.1 | 3 / 17 | |
| 2.1.0 | 3 / 17 | |
| 2.0.9 | 3 / 17 | |
| 2.0.8 | 3 / 17 | |
| 2.0.7 | 3 / 17 | |
| 2.0.6 | 3 / 17 | |
| 2.0.5 | 3 / 17 | |
| 2.0.4 | 3 / 17 | |
| 2.0.3 | 3 / 17 | |
| 2.0.2 | 3 / 17 | |
| 2.0.1 | 3 / 17 | |
| 2.0.0 | 3 / 17 |
v2.112.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.111.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.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.
v2.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[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.