@fluid-topics/ft-copy-block
Copy block
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
Versions (showing 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 2.1.15 | 3 / 0 | |
| 2.1.14 | 3 / 0 | |
| 2.1.12 | 3 / 0 | |
| 2.1.11 | 3 / 0 | |
| 2.1.10 | 3 / 0 | |
| 2.1.9 | 3 / 0 | |
| 2.1.8 | 3 / 0 | |
| 2.1.7 | 3 / 0 | |
| 2.1.6 | 3 / 0 | |
| 2.1.5 | 3 / 0 | |
| 2.1.4 | 3 / 0 | |
| 2.1.3 | 3 / 0 | |
| 2.1.2 | 3 / 0 | |
| 2.1.1 | 3 / 0 | |
| 2.1.0 | 3 / 0 | |
| 2.0.38 | 3 / 0 | |
| 2.0.37 | 3 / 0 | |
| 2.0.36 | 3 / 0 | |
| 2.0.35 | 3 / 0 | |
| 2.0.34 | 3 / 0 | |
| 2.0.33 | 3 / 0 | |
| 2.0.32 | 3 / 0 | |
| 2.0.31 | 3 / 0 | |
| 2.0.30 | 3 / 0 | |
| 2.0.29 | 3 / 0 | |
| 2.0.28 | 3 / 0 | |
| 2.0.27 | 3 / 0 | |
| 2.0.26 | 3 / 0 | |
| 2.0.25 | 3 / 0 | |
| 2.0.24 | 3 / 0 | |
| 2.0.23 | 3 / 0 | |
| 2.0.22 | 3 / 0 | |
| 2.0.21 | 3 / 0 | |
| 2.0.20 | 3 / 0 | |
| 2.0.19 | 3 / 0 | |
| 2.0.18 | 3 / 0 | |
| 2.0.17 | 3 / 0 | |
| 2.0.16 | 3 / 0 | |
| 2.0.15 | 3 / 0 | |
| 2.0.14 | 3 / 0 | |
| 2.0.13 | 3 / 0 | |
| 2.0.12 | 3 / 0 | |
| 2.0.11 | 3 / 0 | |
| 2.0.7 | 3 / 0 | |
| 2.0.6 | 3 / 0 | |
| 2.0.5 | 3 / 0 | |
| 2.0.4 | 3 / 0 | |
| 2.0.3 | 3 / 0 | |
| 2.0.2 | 3 / 0 | |
| 2.0.1 | 3 / 0 | |
| 2.0.0 | 3 / 0 |
v2.1.15
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.