@fluid-experimental/property-common
common functions used in properties
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:events_pkg | AI (dependencies): Standard Node.js events polyfill; stable dependency for this long-lived Microsoft package. | ai | |
| dependencies | unvetted-dep:@types/events_pkg | AI (dependencies): Type definitions for events polyfill; benign for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Monorepo tooling dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:traverse | AI (phantom-deps): Monorepo tooling dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Monorepo tooling dependency; not directly imported by design in this platform-helper package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Microsoft FluidFramework platform-helper package; sparse README/keywords are expected for internal packages. | ai | |
| phantom-deps | phantom-dep:@types/events_pkg | AI (phantom-deps): Framework-scoped type package; loaded by convention in FluidFramework monorepo. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): Monorepo tooling dependency; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.100.0 | 9 / 23 | |
| 2.92.0 | 9 / 23 | |
| 2.82.0 | 9 / 23 | |
| 2.74.0 | 9 / 23 | |
| 2.70.0 | 9 / 23 | |
| 2.61.0 | 9 / 23 | |
| 2.43.0 | 9 / 23 | |
| 2.42.0 | 9 / 23 | |
| 2.41.0 | 9 / 23 | |
| 2.40.0 | 9 / 23 | |
| 2.33.1 | 9 / 23 |
v2.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.