@financial-times/cmp-client
A client-side library to help you add a CMP (currently provided by Sourcepoint) to your application.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dotcom-reliability-kit/client-metrics-web | AI (dependencies): Official FT reliability-kit package, same publisher ecosystem. | ai | |
| phantom-deps | phantom-dep:@dotcom-reliability-kit/client-metrics-web | AI (phantom-deps): Referenced via config, expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:next-session-client | AI (phantom-deps): Declared in package.json but used via config; consistent pattern for this package. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 6.23.3 | 2 / 5 | |
| 6.23.2 | 2 / 5 | |
| 6.23.1 | 2 / 5 | |
| 6.23.0 | 2 / 5 | |
| 6.22.4 | 2 / 5 | |
| 6.22.3 | 2 / 5 | |
| 6.22.2 | 2 / 5 | |
| 6.22.1 | 2 / 5 | |
| 6.22.0 | 2 / 5 | |
| 6.21.2 | 1 / 5 | |
| 6.21.1 | 1 / 5 | |
| 6.21.0 | 1 / 5 | |
| 6.20.1 | 1 / 5 | |
| 6.20.0 | 1 / 5 | |
| 6.19.0 | 1 / 5 | |
| 6.18.3 | 1 / 5 | |
| 6.18.2 | 1 / 5 | |
| 6.18.1 | 1 / 5 | |
| 6.18.0 | 1 / 5 | |
| 6.17.0 | 1 / 5 | |
| 6.16.2 | 1 / 5 | |
| 6.16.1 | 1 / 5 | |
| 6.16.0 | 1 / 5 | |
| 6.15.0 | 1 / 5 | |
| 6.14.0 | 1 / 5 | |
| 6.13.0 | 1 / 5 | |
| 6.12.0 | 1 / 5 | |
| 6.11.4 | 1 / 5 | |
| 6.11.3 | 1 / 5 | |
| 6.11.2 | 1 / 5 | |
| 6.11.1 | 1 / 5 | |
| 6.11.0 | 1 / 5 | |
| 6.10.2 | 1 / 5 | |
| 6.10.1 | 1 / 5 | |
| 6.10.0 | 1 / 5 | |
| 6.9.0 | 1 / 5 | |
| 6.8.1 | 1 / 5 | |
| 6.8.0 | 1 / 5 | |
| 6.7.0 | 1 / 5 | |
| 6.6.0 | 1 / 5 | |
| 6.5.0 | 1 / 5 | |
| 6.4.0 | 1 / 5 | |
| 6.3.1 | 1 / 5 | |
| 6.3.0 | 1 / 5 | |
| 6.2.0 | 1 / 5 | |
| 6.1.2 | 1 / 5 | |
| 6.1.1 | 1 / 5 | |
| 6.1.0 | 1 / 5 | |
| 6.0.2 | 1 / 5 | |
| 6.0.1 | 1 / 5 | |
| 6.0.0 | 1 / 5 |
v6.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.