@fluentui/chart-web-components MIT 32 versions

@fluentui/chart-web-components

npm Repository Homepage

A library of Fluent Chart Web Components

32

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

chrisdholtmiroslavstastnylevithomasonuifabricteamuifrnbotlayershifterjustslonemicrosoft1essopranopillow

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established Microsoft package; provenance absence is metadata signal, not security risk.	ai	2026/05/27
dependencies	unvetted-dep:@fluentui/tokens	AI (dependencies): @fluentui/tokens is part of the same Microsoft Fluent UI monorepo; stable false positive for this package.	ai	2026/05/18
phantom-deps	phantom-dep:tabbable	AI (phantom-deps): Declared runtime dep in package.json; phantom-dep heuristic misfires for this package.	ai	2026/05/06
phantom-deps	phantom-dep:@types/d3-shape	AI (phantom-deps): Type-only dep loaded by convention; stable false positive for this package.	ai	2026/05/06
phantom-deps	phantom-dep:@types/d3-selection	AI (phantom-deps): Type-only dep loaded by convention; stable false positive for this package.	ai	2026/05/06
bogus-package	bogus-package	AI (bogus-package): Legitimate Microsoft Fluent UI component library; README/keyword signals are false positives.	ai	2026/05/06

Versions (showing 32 of 32)

Version	Deps	Published
0.0.78	9 / 4	2026-05-19
0.0.77	9 / 4	2026-05-13
0.0.74	9 / 5	2026-05-06
0.0.72	9 / 5	2026-04-22
0.0.71	9 / 5	2026-04-09
0.0.70	9 / 5	2026-04-07
0.0.69	9 / 5	2026-04-06
0.0.68	9 / 5	2026-04-01
0.0.64	9 / 5	2026-02-23
0.0.62	9 / 5	2026-01-23
0.0.60	9 / 5	2026-01-12
0.0.57	9 / 6	2025-11-07
0.0.56	9 / 6	2025-11-03
0.0.55	9 / 6	2025-10-20
0.0.50	9 / 6	2025-10-06
0.0.49	9 / 6	2025-10-03
0.0.46	9 / 6	2025-09-04
0.0.44	9 / 6	2025-09-01
0.0.42	9 / 6	2025-08-26
0.0.41	9 / 6	2025-08-25
0.0.39	9 / 6	2025-08-04
0.0.38	9 / 6	2025-07-25
0.0.37	9 / 6	2025-07-21
0.0.35	9 / 6	2025-07-01
0.0.34	9 / 6	2025-06-24
0.0.31	9 / 6	2025-06-02
0.0.30	9 / 6	2025-05-28
0.0.28	9 / 6	2025-05-23
0.0.26	9 / 6	2025-05-21
0.0.25	9 / 6	2025-05-20
0.0.23	9 / 6	2025-05-15
0.0.21	9 / 6	2025-05-07

v0.0.78

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.77

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.74

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.72

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.71

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.70

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.69

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.68

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.64

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.62

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.60

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.57

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.56

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.49

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.46

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.44

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.