← Home

@fluidframework/container-runtime

npm Repository Homepage
21
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:@tylerbu/sorted-btree-es6 AI (dependencies): Known FluidFramework-ecosystem fork of sorted-btree; stable dependency across versions of this package. ai
phantom-deps phantom-dep:@tylerbu/sorted-btree-es6 AI (phantom-deps): Referenced in config files only; stable false positive for this package. ai
provenance no-provenance AI (provenance): Large Microsoft OSS monorepo; provenance not yet adopted; stable across versions. ai

Versions (showing 21 of 21)

Version Deps Published
2.111.0 17 / 30
2.110.0 17 / 29
2.103.0 17 / 29
2.102.0 17 / 29
2.101.1 17 / 29
2.101.0 17 / 29
2.100.1 17 / 29
2.100.0 17 / 29
2.93.0 17 / 29
2.92.0 17 / 29
2.91.0 17 / 29
2.90.0 17 / 29
2.83.0 17 / 29
2.82.0 17 / 29
2.81.1 17 / 29
2.81.0 17 / 29
2.80.0 17 / 29
2.74.0 17 / 29
2.73.0 17 / 28
2.72.0 17 / 28
2.71.0 17 / 28

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.91.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.90.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.83.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.82.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.81.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.81.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.80.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.74.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.73.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.72.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.

v2.71.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.