@fluid-experimental/property-changeset
property changeset definitions and related functionalities
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:fastest-json-copy | AI (dependencies): Small trivial JSON-copy utility added by trusted Microsoft monorepo publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft monorepo package; sparse README/keywords are typical for internal library packages. | ai | |
| provenance | no-provenance | AI (provenance): Large Microsoft OSS project; lack of Sigstore provenance is not unusual for this publisher. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 2.112.0 | 7 / 22 | |
| 2.111.0 | 7 / 22 | |
| 2.110.0 | 7 / 22 | |
| 2.103.0 | 7 / 22 | |
| 2.102.0 | 7 / 22 | |
| 2.101.1 | 7 / 22 | |
| 2.101.0 | 7 / 22 | |
| 2.100.1 | 7 / 22 | |
| 2.100.0 | 7 / 22 | |
| 2.93.0 | 7 / 22 | |
| 2.92.0 | 7 / 22 | |
| 2.91.0 | 7 / 22 | |
| 2.90.0 | 7 / 22 | |
| 2.83.0 | 7 / 22 | |
| 2.82.0 | 7 / 22 | |
| 2.81.1 | 7 / 22 | |
| 2.81.0 | 7 / 22 | |
| 2.80.0 | 7 / 22 | |
| 2.74.0 | 7 / 22 | |
| 2.73.0 | 7 / 21 | |
| 2.72.0 | 7 / 21 | |
| 2.71.0 | 7 / 21 | |
| 2.70.0 | 7 / 21 | |
| 2.63.0 | 7 / 21 | |
| 2.62.0 | 7 / 21 | |
| 2.61.0 | 7 / 21 | |
| 2.60.0 | 7 / 21 | |
| 2.53.1 | 7 / 21 | |
| 2.53.0 | 7 / 21 | |
| 2.52.0 | 7 / 21 | |
| 2.51.0 | 7 / 21 | |
| 2.50.0 | 7 / 21 | |
| 2.43.0 | 7 / 21 | |
| 2.42.0 | 7 / 21 | |
| 2.41.0 | 7 / 21 | |
| 2.40.0 | 7 / 21 | |
| 2.33.2 | 7 / 21 | |
| 2.33.1 | 7 / 21 | |
| 2.33.0 | 7 / 21 | |
| 2.32.0 | 7 / 22 | |
| 2.31.1 | 7 / 22 | |
| 2.31.0 | 7 / 22 | |
| 2.30.0 | 7 / 23 | |
| 2.23.0 | 7 / 23 | |
| 2.22.1 | 7 / 23 | |
| 2.22.0 | 7 / 23 | |
| 2.21.0 | 7 / 23 | |
| 2.20.0 | 7 / 23 | |
| 2.13.0 | 7 / 23 | |
| 2.12.0 | 7 / 23 | |
| 2.11.0 | 7 / 23 | |
| 2.10.0 | 7 / 23 | |
| 2.5.0 | 7 / 23 | |
| 2.4.0 | 7 / 23 | |
| 2.3.1 | 7 / 24 | |
| 2.3.0 | 7 / 24 | |
| 2.2.2 | 7 / 24 | |
| 2.2.1 | 7 / 24 | |
| 2.2.0 | 7 / 24 | |
| 2.1.2 | 7 / 24 | |
| 2.1.1 | 7 / 24 | |
| 2.1.0 | 7 / 24 | |
| 2.0.7 | 8 / 24 | |
| 2.0.0 | 8 / 24 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
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.