@fluid-tools/benchmark
Benchmarking tools
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:moment | AI (phantom-deps): moment is a declared runtime dep used in config/build context; phantom-dep heuristic fires but it's a legitimate dependency. | ai | |
| phantom-deps | phantom-dep:mocha-multi-reporters | AI (phantom-deps): mocha-multi-reporters referenced in config files as intended; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.59.0 | 3 / 19 | |
| 0.58.0 | 3 / 18 | |
| 0.57.0 | 3 / 18 | |
| 0.55.0 | 5 / 17 | |
| 0.54.0 | 5 / 17 | |
| 0.53.0 | 5 / 17 | |
| 0.52.0 | 5 / 15 | |
| 0.51.0 | 6 / 14 |
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.