@fluid-topics/ft-reader-topic-content
Content of a topic in integrated reader.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): rtellier is an established publisher (7 approved packages) within the same antidot.net org; transition appears legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Mature org package with 380 versions; no provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:@fluid-topics/ft-chip | AI (phantom-deps): Same-org component dep; likely used indirectly via peer/transitive patterns in this component library. | ai | |
| phantom-deps | phantom-dep:@fluid-topics/ft-tooltip | AI (phantom-deps): Same-org component dep; likely used indirectly via peer/transitive patterns in this component library. | ai |
Versions (showing 51 of 112)
| Version | Deps | Published |
|---|---|---|
| 2.1.15 | 8 / 0 | |
| 2.1.14 | 8 / 0 | |
| 2.1.12 | 8 / 0 | |
| 2.1.11 | 8 / 0 | |
| 2.1.10 | 8 / 0 | |
| 2.1.9 | 8 / 0 | |
| 2.1.8 | 8 / 0 | |
| 2.1.7 | 8 / 0 | |
| 2.1.6 | 8 / 0 | |
| 2.1.5 | 8 / 0 | |
| 2.1.4 | 8 / 0 | |
| 2.1.3 | 8 / 0 | |
| 2.1.2 | 8 / 0 | |
| 2.1.1 | 8 / 0 | |
| 2.1.0 | 8 / 0 | |
| 2.0.38 | 8 / 0 | |
| 2.0.37 | 8 / 0 | |
| 2.0.36 | 8 / 0 | |
| 2.0.35 | 8 / 0 | |
| 2.0.34 | 8 / 0 | |
| 2.0.33 | 8 / 0 | |
| 2.0.32 | 8 / 0 | |
| 2.0.31 | 8 / 0 | |
| 2.0.30 | 8 / 0 | |
| 2.0.29 | 8 / 0 | |
| 2.0.28 | 8 / 0 | |
| 2.0.27 | 8 / 0 | |
| 2.0.26 | 8 / 0 | |
| 2.0.25 | 8 / 0 | |
| 2.0.24 | 8 / 0 | |
| 2.0.23 | 8 / 0 | |
| 2.0.22 | 8 / 0 | |
| 2.0.21 | 8 / 0 | |
| 2.0.20 | 8 / 0 | |
| 2.0.19 | 8 / 0 | |
| 2.0.18 | 8 / 0 | |
| 2.0.17 | 8 / 0 | |
| 2.0.16 | 8 / 0 | |
| 2.0.15 | 8 / 0 | |
| 2.0.14 | 8 / 0 | |
| 2.0.13 | 8 / 0 | |
| 2.0.12 | 8 / 0 | |
| 2.0.11 | 8 / 0 | |
| 2.0.10 | 8 / 0 | |
| 2.0.9 | 8 / 0 | |
| 2.0.8 | 8 / 0 | |
| 2.0.7 | 8 / 0 | |
| 2.0.6 | 8 / 0 | |
| 2.0.5 | 8 / 0 | |
| 2.0.4 | 8 / 0 | |
| 2.0.3 | 8 / 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.