@fluidframework/container-loader
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:@types/events_pkg | AI (dependencies): Standard npm:@types/events alias; type-only dev dependency, no runtime risk. | ai | |
| phantom-deps | phantom-dep:@types/events_pkg | AI (phantom-deps): Type-only package; not imported at runtime by design. | ai | |
| dependencies | unvetted-dep:events_pkg | AI (dependencies): events_pkg is a standard npm alias for the 'events' polyfill package; stable pattern across FluidFramework versions. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get inside a Proxy trap is idiomatic JS; not obfuscation for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.100.0 | 11 / 28 | |
| 2.92.0 | 12 / 29 | |
| 2.71.0 | 13 / 27 | |
| 2.63.0 | 13 / 27 | |
| 2.53.1 | 13 / 27 | |
| 2.52.0 | 13 / 27 | |
| 2.50.0 | 13 / 28 | |
| 2.40.0 | 13 / 28 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.71.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.63.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.53.1
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.52.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.50.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.40.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.