@justeattakeaway/pie-notification
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 JEA org package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 0.24.11 | 3 / 4 | |
| 0.24.10 | 3 / 4 | |
| 0.24.9 | 3 / 4 | |
| 0.24.8 | 3 / 4 | |
| 0.24.7 | 3 / 4 | |
| 0.24.6 | 3 / 4 | |
| 0.24.5 | 3 / 4 | |
| 0.24.4 | 3 / 4 | |
| 0.24.3 | 3 / 4 | |
| 0.24.2 | 3 / 4 | |
| 0.24.1 | 3 / 4 | |
| 0.24.0 | 3 / 4 | |
| 0.23.4 | 3 / 4 | |
| 0.23.3 | 3 / 4 | |
| 0.23.2 | 3 / 4 | |
| 0.23.1 | 3 / 4 | |
| 0.23.0 | 3 / 4 | |
| 0.22.0 | 3 / 4 | |
| 0.21.25 | 3 / 4 | |
| 0.21.24 | 3 / 6 | |
| 0.21.23 | 3 / 6 | |
| 0.21.22 | 3 / 6 | |
| 0.21.21 | 3 / 6 | |
| 0.21.20 | 3 / 6 | |
| 0.21.19 | 3 / 6 | |
| 0.21.18 | 3 / 6 | |
| 0.21.17 | 3 / 6 | |
| 0.21.16 | 3 / 6 | |
| 0.21.15 | 3 / 6 | |
| 0.21.14 | 3 / 6 | |
| 0.21.13 | 3 / 6 | |
| 0.21.12 | 3 / 6 | |
| 0.21.11 | 3 / 6 | |
| 0.21.10 | 3 / 6 | |
| 0.21.9 | 3 / 6 | |
| 0.21.8 | 3 / 6 | |
| 0.21.7 | 3 / 6 | |
| 0.21.6 | 3 / 6 | |
| 0.21.5 | 3 / 6 | |
| 0.21.4 | 3 / 6 | |
| 0.21.3 | 3 / 6 | |
| 0.21.2 | 3 / 6 | |
| 0.21.1 | 3 / 6 | |
| 0.21.0 | 3 / 6 | |
| 0.20.3 | 3 / 6 | |
| 0.20.2 | 3 / 6 | |
| 0.20.1 | 3 / 6 | |
| 0.20.0 | 3 / 6 | |
| 0.19.0 | 3 / 6 | |
| 0.18.3 | 3 / 6 | |
| 0.18.2 | 3 / 6 | |
| 0.18.1 | 3 / 6 | |
| 0.18.0 | 3 / 6 | |
| 0.17.0 | 3 / 6 | |
| 0.16.2 | 3 / 6 | |
| 0.16.1 | 3 / 6 | |
| 0.16.0 | 3 / 6 | |
| 0.15.1 | 3 / 6 | |
| 0.15.0 | 3 / 6 | |
| 0.14.10 | 3 / 6 | |
| 0.14.9 | 3 / 6 | |
| 0.14.8 | 3 / 6 | |
| 0.14.7 | 3 / 6 | |
| 0.14.6 | 3 / 6 | |
| 0.14.5 | 3 / 6 | |
| 0.14.4 | 3 / 6 | |
| 0.14.3 | 3 / 6 | |
| 0.14.2 | 3 / 6 | |
| 0.14.1 | 3 / 6 | |
| 0.14.0 | 3 / 6 | |
| 0.13.4 | 3 / 6 | |
| 0.13.3 | 3 / 6 | |
| 0.13.2 | 3 / 6 | |
| 0.13.1 | 3 / 6 | |
| 0.13.0 | 3 / 6 | |
| 0.12.15 | 3 / 5 | |
| 0.12.14 | 3 / 5 | |
| 0.12.13 | 3 / 5 | |
| 0.12.12 | 3 / 5 | |
| 0.12.11 | 3 / 5 | |
| 0.12.10 | 3 / 5 | |
| 0.12.9 | 3 / 5 | |
| 0.12.8 | 3 / 5 | |
| 0.12.7 | 3 / 5 | |
| 0.12.6 | 3 / 5 | |
| 0.12.5 | 3 / 5 | |
| 0.12.4 | 3 / 5 | |
| 0.12.3 | 3 / 5 | |
| 0.12.2 | 3 / 5 | |
| 0.12.1 | 3 / 5 | |
| 0.12.0 | 3 / 5 | |
| 0.11.0 | 3 / 5 | |
| 0.10.2 | 3 / 5 | |
| 0.10.1 | 3 / 5 | |
| 0.10.0 | 3 / 5 | |
| 0.9.3 | 3 / 4 | |
| 0.9.2 | 3 / 4 | |
| 0.9.1 | 3 / 4 | |
| 0.9.0 | 3 / 4 | |
| 0.8.0 | 3 / 4 |
v0.24.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.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.13.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.13.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.12.15
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.12.14
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.12.13
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.12.12
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.12.11
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.12.10
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.12.9
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.12.8
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.12.7
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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.11.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.10.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.10.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.10.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.9.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.9.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.9.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.9.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.8.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.