@justeattakeaway/pie-text-input
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established JustEatTakeaway monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 0.30.6 | 3 / 5 | |
| 0.30.5 | 3 / 5 | |
| 0.30.4 | 3 / 5 | |
| 0.30.3 | 3 / 5 | |
| 0.30.2 | 3 / 5 | |
| 0.30.1 | 3 / 5 | |
| 0.30.0 | 3 / 5 | |
| 0.29.37 | 3 / 5 | |
| 0.29.36 | 3 / 5 | |
| 0.29.35 | 3 / 5 | |
| 0.29.34 | 3 / 5 | |
| 0.29.33 | 3 / 5 | |
| 0.29.32 | 3 / 5 | |
| 0.29.31 | 3 / 5 | |
| 0.29.30 | 3 / 5 | |
| 0.29.29 | 3 / 7 | |
| 0.29.28 | 3 / 7 | |
| 0.29.27 | 3 / 7 | |
| 0.29.26 | 3 / 7 | |
| 0.29.25 | 3 / 7 | |
| 0.29.24 | 3 / 7 | |
| 0.29.23 | 3 / 7 | |
| 0.29.22 | 3 / 7 | |
| 0.29.21 | 3 / 7 | |
| 0.29.20 | 3 / 7 | |
| 0.29.19 | 3 / 7 | |
| 0.29.18 | 3 / 7 | |
| 0.29.17 | 3 / 7 | |
| 0.29.16 | 3 / 7 | |
| 0.29.15 | 3 / 7 | |
| 0.29.14 | 3 / 7 | |
| 0.29.13 | 3 / 7 | |
| 0.29.12 | 3 / 7 | |
| 0.29.11 | 3 / 7 | |
| 0.29.10 | 3 / 7 | |
| 0.29.9 | 3 / 7 | |
| 0.29.8 | 3 / 7 | |
| 0.29.7 | 3 / 7 | |
| 0.29.6 | 3 / 7 | |
| 0.29.5 | 3 / 7 | |
| 0.29.4 | 3 / 7 | |
| 0.29.3 | 3 / 7 | |
| 0.29.2 | 3 / 7 | |
| 0.29.1 | 3 / 7 | |
| 0.29.0 | 3 / 7 | |
| 0.28.12 | 3 / 7 | |
| 0.28.11 | 3 / 7 | |
| 0.28.10 | 3 / 7 | |
| 0.28.9 | 3 / 7 | |
| 0.28.8 | 3 / 7 | |
| 0.28.7 | 3 / 7 | |
| 0.28.6 | 3 / 7 | |
| 0.28.5 | 3 / 7 | |
| 0.28.4 | 3 / 7 | |
| 0.28.3 | 3 / 7 | |
| 0.28.2 | 3 / 7 | |
| 0.28.1 | 3 / 7 | |
| 0.28.0 | 3 / 7 | |
| 0.27.6 | 3 / 7 | |
| 0.27.5 | 3 / 7 | |
| 0.27.4 | 3 / 7 | |
| 0.27.3 | 3 / 7 | |
| 0.27.2 | 3 / 7 | |
| 0.27.1 | 3 / 7 | |
| 0.27.0 | 3 / 7 | |
| 0.26.2 | 3 / 6 | |
| 0.26.1 | 3 / 6 | |
| 0.26.0 | 3 / 6 | |
| 0.25.3 | 3 / 6 | |
| 0.25.2 | 3 / 6 | |
| 0.25.1 | 3 / 6 | |
| 0.25.0 | 3 / 6 | |
| 0.24.6 | 3 / 6 | |
| 0.24.5 | 3 / 6 | |
| 0.24.4 | 3 / 6 | |
| 0.24.3 | 3 / 6 | |
| 0.24.2 | 3 / 6 | |
| 0.24.1 | 3 / 6 | |
| 0.24.0 | 3 / 6 | |
| 0.23.6 | 3 / 6 | |
| 0.23.5 | 3 / 6 | |
| 0.23.4 | 3 / 6 | |
| 0.23.3 | 3 / 6 | |
| 0.23.2 | 3 / 5 | |
| 0.23.1 | 3 / 5 | |
| 0.23.0 | 3 / 5 | |
| 0.22.2 | 3 / 5 | |
| 0.22.1 | 3 / 5 | |
| 0.22.0 | 3 / 5 | |
| 0.21.0 | 3 / 5 | |
| 0.20.0 | 3 / 5 |
v0.30.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.