@fluid-experimental/ot MIT 34 versions

@fluid-experimental/ot

npm Repository Homepage

Distributed data structure for hosting ottypes

34

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ms-fluid-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped Microsoft FluidFramework package; 'ot' suffix match to 'got' is a false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:koa	AI (typosquat): Scoped Microsoft FluidFramework package; Levenshtein match to 'koa' is a false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped Microsoft FluidFramework package; Levenshtein match to 'pg' is a false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped Microsoft FluidFramework package; Levenshtein match to 'qs' is a false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped Microsoft FluidFramework package; Levenshtein match to 'joi' is a false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:zod	AI (typosquat): Scoped Microsoft FluidFramework package; Levenshtein match to 'zod' is a false positive.	ai	2026/04/30
phantom-deps	phantom-dep:@fluidframework/core-interfaces	AI (phantom-deps): FluidFramework monorepo package; peer/transitive usage via config files is expected.	ai	2026/04/30
phantom-deps	phantom-dep:@fluidframework/driver-definitions	AI (phantom-deps): FluidFramework monorepo package; indirect usage via config files is expected.	ai	2026/04/30

Versions (showing 34 of 34)

Version	Deps	Published
2.102.0	7 / 24	2026-05-29
2.101.1	7 / 24	2026-05-20
2.101.0	7 / 24	2026-05-13
2.100.1	7 / 24	2026-05-20
2.100.0	7 / 24	2026-04-28
2.93.0	7 / 24	2026-04-16
2.92.0	7 / 24	2026-04-01
2.91.0	7 / 24	2026-03-18
2.90.0	7 / 24	2026-03-03
2.83.0	7 / 24	2026-02-18
2.82.0	7 / 24	2026-02-04
2.81.1	7 / 24	2026-01-28
2.81.0	7 / 24	2026-01-21
2.80.0	7 / 24	2026-01-06
2.74.0	7 / 24	2025-12-15
2.73.0	7 / 23	2025-11-24
2.72.0	7 / 23	2025-11-11
2.71.0	7 / 23	2025-11-03
2.70.0	7 / 23	2025-10-28
2.63.0	7 / 23	2025-10-14
2.62.0	7 / 23	2025-09-30
2.61.0	7 / 23	2025-09-23
2.60.0	7 / 23	2025-09-02
2.53.1	7 / 23	2025-08-25
2.53.0	7 / 23	2025-08-18
2.52.0	7 / 23	2025-08-04
2.51.0	7 / 23	2025-07-21
2.50.0	7 / 23	2025-07-07
2.43.0	7 / 23	2025-06-23
2.42.0	7 / 23	2025-06-10
2.41.0	7 / 23	2025-05-27
2.40.0	7 / 23	2025-05-12
2.33.2	7 / 23	2025-05-01
2.33.1	7 / 23	2025-04-30

v2.102.0

1 finding

LOW No provenance attestation provenance

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

v2.101.1

1 finding

LOW No provenance attestation provenance

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

v2.101.0

1 finding

LOW No provenance attestation provenance

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

v2.100.1

1 finding

LOW No provenance attestation provenance

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

v2.100.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'got' typosquat

Package name '@fluid-experimental/ot' is 1 edit(s) away from popular package 'got'.

LOW No provenance attestation provenance

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

v2.93.0

1 finding

LOW No provenance attestation provenance

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

v2.92.0

1 finding

LOW No provenance attestation provenance

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

v2.91.0

1 finding

LOW No provenance attestation provenance

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

v2.90.0

1 finding

LOW No provenance attestation provenance

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

v2.83.0

1 finding

LOW No provenance attestation provenance

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

v2.82.0

1 finding

LOW No provenance attestation provenance

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

v2.81.1

1 finding

LOW No provenance attestation provenance

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

v2.81.0

1 finding

LOW No provenance attestation provenance

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

v2.80.0

1 finding

LOW No provenance attestation provenance

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

v2.74.0

1 finding

LOW No provenance attestation provenance

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

v2.73.0

1 finding

LOW No provenance attestation provenance

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

v2.72.0

1 finding

LOW No provenance attestation provenance

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

v2.71.0

1 finding

LOW No provenance attestation provenance

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

v2.70.0

1 finding

LOW No provenance attestation provenance

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

v2.63.0

1 finding

LOW No provenance attestation provenance

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

v2.62.0

1 finding

LOW No provenance attestation provenance

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

v2.61.0

1 finding

LOW No provenance attestation provenance

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

v2.60.0

1 finding

LOW No provenance attestation provenance

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

v2.53.1

1 finding

LOW No provenance attestation provenance

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

v2.53.0

1 finding

LOW No provenance attestation provenance

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

v2.52.0

1 finding

LOW No provenance attestation provenance

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

v2.51.0

1 finding

LOW No provenance attestation provenance

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

v2.50.0

1 finding

LOW No provenance attestation provenance

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

v2.43.0

1 finding

LOW No provenance attestation provenance

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

v2.42.0

1 finding

LOW No provenance attestation provenance

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

v2.41.0

1 finding

LOW No provenance attestation provenance

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

v2.40.0

1 finding

LOW No provenance attestation provenance

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

v2.33.2

1 finding

LOW No provenance attestation provenance

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

v2.33.1

1 finding

LOW No provenance attestation provenance

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