← Home

@fluid-experimental/dds-interceptions

npm Repository Homepage

Distributed Data Structures that support an interception callback

51
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, 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
provenance no-provenance AI (provenance): Microsoft FluidFramework monorepo; provenance not yet configured but publisher and repo are well-established. ai

Versions (showing 51 of 72)

View all versions
Version Deps Published
2.112.0 5 / 23
2.111.0 5 / 23
2.110.0 5 / 23
2.103.0 5 / 23
2.102.0 5 / 23
2.101.1 5 / 23
2.101.0 5 / 23
2.100.1 5 / 23
2.100.0 5 / 23
2.93.0 5 / 23
2.92.0 5 / 23
2.91.0 5 / 23
2.90.0 5 / 23
2.83.0 5 / 23
2.82.0 5 / 23
2.81.1 5 / 23
2.81.0 5 / 23
2.80.0 5 / 23
2.74.0 5 / 23
2.73.0 5 / 22
2.72.0 5 / 22
2.71.0 5 / 22
2.70.0 5 / 22
2.63.0 5 / 22
2.62.0 5 / 22
2.61.0 5 / 22
2.60.0 5 / 22
2.53.1 5 / 22
2.53.0 5 / 22
2.52.0 5 / 22
2.51.0 5 / 22
2.50.0 5 / 22
2.43.0 5 / 22
2.42.0 5 / 22
2.41.0 5 / 22
2.40.0 5 / 22
2.33.2 5 / 22
2.33.1 5 / 22
2.33.0 5 / 22
2.32.0 5 / 23
2.31.1 5 / 23
2.31.0 5 / 23
2.30.0 5 / 24
2.23.0 5 / 24
2.22.1 5 / 24
2.22.0 5 / 24
2.21.0 5 / 24
2.20.0 5 / 24
2.13.0 5 / 24
2.12.0 5 / 24
2.11.0 5 / 24

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