@fluidframework/id-compressor
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tylerbu/sorted-btree-es6 | AI (dependencies): Known FluidFramework dependency; ES6 fork of sorted-btree used consistently across versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package; provenance not yet adopted by this publisher across the ecosystem. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 2.112.0 | 6 / 23 | |
| 2.111.0 | 6 / 23 | |
| 2.110.0 | 6 / 23 | |
| 2.103.0 | 6 / 23 | |
| 2.102.0 | 6 / 23 | |
| 2.101.1 | 6 / 23 | |
| 2.101.0 | 6 / 23 | |
| 2.100.1 | 6 / 23 | |
| 2.100.0 | 6 / 23 | |
| 2.93.0 | 6 / 23 | |
| 2.92.0 | 6 / 23 | |
| 2.91.0 | 6 / 23 | |
| 2.90.0 | 6 / 23 | |
| 2.83.0 | 6 / 23 | |
| 2.82.0 | 6 / 23 | |
| 2.81.1 | 6 / 23 | |
| 2.81.0 | 6 / 23 | |
| 2.80.0 | 6 / 23 | |
| 2.74.0 | 6 / 23 | |
| 2.73.0 | 6 / 22 | |
| 2.72.0 | 6 / 22 | |
| 2.71.0 | 6 / 22 | |
| 2.70.0 | 6 / 22 | |
| 2.63.0 | 6 / 22 | |
| 2.62.0 | 6 / 22 | |
| 2.61.0 | 6 / 22 | |
| 2.60.0 | 6 / 22 | |
| 2.53.1 | 6 / 22 | |
| 2.53.0 | 6 / 22 | |
| 2.52.0 | 6 / 22 | |
| 2.51.0 | 6 / 22 | |
| 2.50.0 | 6 / 23 | |
| 2.43.0 | 6 / 23 | |
| 2.42.0 | 6 / 23 | |
| 2.41.0 | 6 / 23 | |
| 2.40.0 | 6 / 23 | |
| 2.33.2 | 6 / 23 | |
| 2.33.1 | 6 / 23 | |
| 2.33.0 | 6 / 23 | |
| 2.32.0 | 6 / 24 | |
| 2.31.1 | 6 / 24 | |
| 2.31.0 | 6 / 24 | |
| 2.30.0 | 6 / 25 | |
| 2.23.0 | 6 / 25 | |
| 2.22.1 | 6 / 25 | |
| 2.22.0 | 6 / 25 | |
| 2.21.0 | 6 / 25 | |
| 2.20.0 | 6 / 25 | |
| 2.13.0 | 6 / 25 | |
| 2.12.0 | 6 / 25 | |
| 2.11.0 | 6 / 25 | |
| 2.10.0 | 6 / 25 | |
| 2.5.0 | 6 / 25 | |
| 2.4.0 | 6 / 25 | |
| 2.3.1 | 6 / 26 | |
| 2.3.0 | 6 / 26 | |
| 2.2.2 | 6 / 26 | |
| 2.2.1 | 6 / 26 | |
| 2.2.0 | 6 / 26 | |
| 2.1.2 | 6 / 26 | |
| 2.1.1 | 6 / 26 | |
| 2.1.0 | 6 / 26 | |
| 2.0.9 | 6 / 26 | |
| 2.0.8 | 6 / 26 | |
| 2.0.7 | 6 / 26 | |
| 2.0.6 | 6 / 26 | |
| 2.0.5 | 6 / 26 | |
| 2.0.4 | 6 / 26 | |
| 2.0.3 | 6 / 26 | |
| 2.0.2 | 6 / 26 | |
| 2.0.1 | 6 / 26 | |
| 2.0.0 | 6 / 26 |
v2.112.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.111.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.