← Home

@fluidframework/test-runtime-utils

72
Versions
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ms-fluid-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@fluidframework/core-utils AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern across all versions. ai
dependencies unvetted-dep:@fluid-internal/client-utils AI (dependencies): Sibling FluidFramework internal package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/driver-utils AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/id-compressor AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/runtime-utils AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/core-interfaces AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/telemetry-utils AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/driver-definitions AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/runtime-definitions AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/routerlicious-driver AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/container-definitions AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/datastore-definitions AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
dependencies unvetted-dep:@fluidframework/container-runtime-definitions AI (dependencies): Sibling FluidFramework package from same monorepo; stable pattern. ai
provenance no-provenance AI (provenance): Established Microsoft package; lack of Sigstore provenance is common for this ecosystem and not a risk signal here. ai

Versions (showing 72 of 72)

Version Deps Published
2.112.0 15 / 22
2.111.0 15 / 22
2.110.0 15 / 22
2.103.0 15 / 22
2.102.0 15 / 22
2.101.1 15 / 22
2.101.0 15 / 22
2.100.1 15 / 22
2.100.0 15 / 22
2.93.0 15 / 22
2.92.0 15 / 22
2.91.0 15 / 22
2.90.0 15 / 22
2.83.0 15 / 22
2.82.0 15 / 22
2.81.1 15 / 22
2.81.0 15 / 22
2.80.0 15 / 22
2.74.0 15 / 22
2.73.0 15 / 21
2.72.0 15 / 21
2.71.0 15 / 21
2.70.0 15 / 21
2.63.0 15 / 21
2.62.0 15 / 21
2.61.0 15 / 21
2.60.0 15 / 21
2.53.1 15 / 21
2.53.0 15 / 21
2.52.0 15 / 21
2.51.0 15 / 21
2.50.0 14 / 22
2.43.0 14 / 22
2.42.0 14 / 22
2.41.0 14 / 22
2.40.0 14 / 22
2.33.2 14 / 22
2.33.1 14 / 22
2.33.0 14 / 22
2.32.0 14 / 23
2.31.1 14 / 23
2.31.0 14 / 23
2.30.0 14 / 24
2.23.0 14 / 24
2.22.1 14 / 24
2.22.0 14 / 24
2.21.0 14 / 24
2.20.0 14 / 24
2.13.0 14 / 24
2.12.0 14 / 24
2.11.0 14 / 24
2.10.0 14 / 24
2.5.0 14 / 24
2.4.0 14 / 24
2.3.1 14 / 25
2.3.0 14 / 25
2.2.2 14 / 25
2.2.1 14 / 25
2.2.0 14 / 25
2.1.2 14 / 25
2.1.1 14 / 25
2.1.0 14 / 25
2.0.9 14 / 25
2.0.8 14 / 25
2.0.7 14 / 25
2.0.6 14 / 25
2.0.5 14 / 25
2.0.4 14 / 25
2.0.3 14 / 25
2.0.2 14 / 25
2.0.1 14 / 25
2.0.0 14 / 25

v2.112.0

1 finding
INFO No provenance attestation provenance

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

v2.111.0

1 finding
INFO No provenance attestation provenance

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

v2.33.0

1 finding
INFO No provenance attestation provenance

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

v2.32.0

1 finding
INFO No provenance attestation provenance

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

v2.31.1

1 finding
INFO No provenance attestation provenance

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

v2.31.0

1 finding
INFO No provenance attestation provenance

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

v2.30.0

1 finding
INFO No provenance attestation provenance

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

v2.23.0

1 finding
INFO No provenance attestation provenance

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

v2.22.1

1 finding
INFO No provenance attestation provenance

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

v2.22.0

1 finding
INFO No provenance attestation provenance

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

v2.21.0

1 finding
INFO No provenance attestation provenance

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

v2.20.0

1 finding
INFO No provenance attestation provenance

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

v2.13.0

1 finding
INFO No provenance attestation provenance

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

v2.12.0

1 finding
INFO No provenance attestation provenance

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

v2.11.0

1 finding
INFO No provenance attestation provenance

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

v2.10.0

1 finding
INFO No provenance attestation provenance

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

v2.5.0

1 finding
INFO No provenance attestation provenance

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

v2.4.0

1 finding
INFO No provenance attestation provenance

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

v2.3.1

1 finding
INFO No provenance attestation provenance

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

v2.3.0

1 finding
INFO No provenance attestation provenance

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

v2.2.2

1 finding
INFO No provenance attestation provenance

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

v2.2.1

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
INFO No provenance attestation provenance

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

v2.1.2

1 finding
INFO No provenance attestation provenance

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

v2.1.1

1 finding
INFO No provenance attestation provenance

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

v2.1.0

1 finding
INFO No provenance attestation provenance

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

v2.0.9

1 finding
INFO No provenance attestation provenance

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

v2.0.8

1 finding
INFO No provenance attestation provenance

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

v2.0.7

1 finding
INFO No provenance attestation provenance

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

v2.0.6

1 finding
INFO No provenance attestation provenance

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

v2.0.5

1 finding
INFO No provenance attestation provenance

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

v2.0.4

1 finding
INFO No provenance attestation provenance

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

v2.0.3

1 finding
INFO No provenance attestation provenance

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

v2.0.2

1 finding
INFO No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

1 finding
INFO No provenance attestation provenance

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