@fluid-experimental/data-object-base MIT 34 versions

@fluid-experimental/data-object-base

npm Repository Homepage

Data object base for synchronously and lazily loaded object scenarios

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
phantom-deps	phantom-dep:@fluidframework/datastore	AI (phantom-deps): TypeScript package; deps referenced in config/type exports, not direct imports. Stable FP for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@fluidframework/core-utils	AI (phantom-deps): Same pattern — config-referenced sibling dep, stable FP.	ai	2026/04/30
phantom-deps	phantom-dep:@fluid-internal/client-utils	AI (phantom-deps): Same pattern — config-referenced sibling dep, stable FP.	ai	2026/04/30
phantom-deps	phantom-dep:@fluidframework/request-handler	AI (phantom-deps): Same pattern — config-referenced sibling dep, stable FP.	ai	2026/04/30
phantom-deps	phantom-dep:@fluidframework/shared-object-base	AI (phantom-deps): Same pattern — config-referenced sibling dep, stable FP.	ai	2026/04/30
phantom-deps	phantom-dep:@fluidframework/datastore-definitions	AI (phantom-deps): Same pattern — config-referenced sibling dep, stable FP.	ai	2026/04/30

Versions (showing 34 of 34)

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

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

1 finding

LOW No provenance attestation provenance

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

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.