@financial-times/privacy-us-privacy
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@financial-times/privacy-legislation-client | AI (phantom-deps): Same org scope; likely re-exported rather than directly imported. Stable false positive for this package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 6.23.2 | 1 / 7 | |
| 6.23.1 | 1 / 7 | |
| 6.23.0 | 1 / 7 | |
| 6.22.4 | 1 / 7 | |
| 6.22.3 | 1 / 7 | |
| 6.22.2 | 1 / 7 | |
| 6.22.1 | 1 / 7 | |
| 6.22.0 | 1 / 7 | |
| 6.21.2 | 1 / 7 | |
| 6.21.1 | 1 / 7 | |
| 6.21.0 | 1 / 7 | |
| 6.20.1 | 1 / 7 | |
| 6.20.0 | 1 / 7 | |
| 6.19.0 | 1 / 7 | |
| 6.18.3 | 1 / 7 | |
| 6.18.2 | 1 / 7 | |
| 6.18.1 | 1 / 7 | |
| 6.18.0 | 1 / 7 | |
| 6.17.0 | 1 / 7 | |
| 6.16.2 | 1 / 7 | |
| 6.16.1 | 1 / 7 | |
| 6.16.0 | 1 / 7 | |
| 6.15.0 | 1 / 7 | |
| 6.14.0 | 1 / 7 | |
| 6.13.0 | 1 / 7 | |
| 6.12.0 | 1 / 7 | |
| 6.11.4 | 1 / 7 | |
| 6.11.3 | 1 / 7 | |
| 6.11.2 | 1 / 7 | |
| 6.11.1 | 1 / 7 | |
| 6.11.0 | 1 / 7 | |
| 6.10.2 | 1 / 7 | |
| 6.10.1 | 1 / 7 | |
| 6.10.0 | 1 / 7 | |
| 6.9.0 | 1 / 7 | |
| 6.8.1 | 1 / 7 | |
| 6.8.0 | 1 / 7 | |
| 6.7.0 | 1 / 7 | |
| 6.6.0 | 1 / 7 | |
| 6.5.0 | 1 / 7 | |
| 6.4.0 | 1 / 7 | |
| 6.3.1 | 1 / 7 | |
| 6.3.0 | 1 / 7 | |
| 6.2.0 | 1 / 7 | |
| 6.1.2 | 1 / 7 | |
| 6.1.1 | 1 / 7 | |
| 6.1.0 | 1 / 7 | |
| 6.0.2 | 1 / 7 | |
| 6.0.1 | 1 / 7 | |
| 6.0.0 | 1 / 7 |
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.