@fluid-internal/client-utils
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; GitHub repo provenance is documented and stable. | ai | |
| dependencies | unvetted-dep:events_pkg | AI (dependencies): events is a well-known Node.js EventEmitter polyfill; aliased via npm: protocol, stable for this package. | ai | |
| dependencies | unvetted-dep:@types/events_pkg | AI (dependencies): @types/events is the corresponding type definitions; aliased via npm: protocol, stable for this package. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is a declared runtime dep used for browser polyfill; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@types/events_pkg | AI (phantom-deps): Framework-scoped type package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fluidframework/core-utils | AI (phantom-deps): Referenced in config files; stable false positive for this FluidFramework package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.100.1 | 7 / 37 | |
| 2.100.0 | 7 / 37 | |
| 2.93.0 | 7 / 37 | |
| 2.83.0 | 7 / 37 | |
| 2.74.0 | 7 / 37 | |
| 2.62.0 | 7 / 36 | |
| 2.42.0 | 7 / 36 | |
| 2.41.0 | 7 / 36 | |
| 2.33.2 | 7 / 36 |
v2.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.83.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.62.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.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.