@fluid-topics/ft-notice
Notice to display different messages
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fluid-topics/design-system-variables | AI (dependencies): Internal @fluid-topics org dependency; consistent with the rest of the package's dependency graph. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with 438 versions; lack of provenance is consistent across all releases and not a risk indicator here. | ai |
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 2.1.15 | 5 / 0 | |
| 2.1.14 | 5 / 0 | |
| 2.1.12 | 5 / 0 | |
| 2.1.11 | 5 / 0 | |
| 2.1.10 | 5 / 0 | |
| 2.1.9 | 5 / 0 | |
| 2.1.8 | 5 / 0 | |
| 2.1.7 | 5 / 0 | |
| 2.1.6 | 5 / 0 | |
| 2.1.5 | 5 / 0 | |
| 2.1.4 | 5 / 0 | |
| 2.1.3 | 5 / 0 | |
| 2.1.2 | 5 / 0 | |
| 2.1.1 | 5 / 0 | |
| 2.1.0 | 5 / 0 | |
| 2.0.38 | 5 / 0 | |
| 2.0.37 | 5 / 0 | |
| 2.0.36 | 5 / 0 | |
| 2.0.35 | 5 / 0 | |
| 2.0.34 | 5 / 0 | |
| 2.0.33 | 5 / 0 | |
| 2.0.32 | 5 / 0 | |
| 2.0.31 | 5 / 0 | |
| 2.0.30 | 5 / 0 | |
| 2.0.29 | 5 / 0 | |
| 2.0.28 | 5 / 0 | |
| 2.0.27 | 5 / 0 | |
| 2.0.26 | 5 / 0 | |
| 2.0.25 | 5 / 0 | |
| 2.0.24 | 5 / 0 | |
| 2.0.23 | 5 / 0 | |
| 2.0.22 | 5 / 0 | |
| 2.0.21 | 5 / 0 | |
| 2.0.20 | 5 / 0 | |
| 2.0.19 | 5 / 0 | |
| 2.0.18 | 5 / 0 | |
| 2.0.17 | 5 / 0 | |
| 2.0.16 | 5 / 0 | |
| 2.0.15 | 5 / 0 | |
| 2.0.14 | 5 / 0 | |
| 2.0.13 | 5 / 0 | |
| 2.0.12 | 5 / 0 | |
| 2.0.11 | 5 / 0 | |
| 2.0.10 | 5 / 0 | |
| 2.0.9 | 5 / 0 | |
| 2.0.7 | 5 / 0 | |
| 2.0.6 | 5 / 0 | |
| 2.0.5 | 5 / 0 | |
| 2.0.4 | 5 / 0 | |
| 2.0.3 | 5 / 0 | |
| 2.0.2 | 5 / 0 |
v2.1.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rtellier) than the most recent previously approved version (antidot) on 2026-07-27, but rtellier is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.