@asicupv/paella-core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ferserc1/input-style-unifier | AI (phantom-deps): Declared dep from same author; used in config/build tooling rather than direct import — stable false positive for this package. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 2.12.11 | 1 / 4 | |
| 2.12.10 | 1 / 4 | |
| 2.12.9 | 1 / 4 | |
| 2.12.8 | 1 / 4 | |
| 2.12.7 | 1 / 4 | |
| 2.12.6 | 1 / 4 | |
| 2.12.5 | 1 / 4 | |
| 2.12.4 | 1 / 4 | |
| 2.12.3 | 1 / 4 | |
| 2.12.2 | 1 / 5 | |
| 2.12.1 | 1 / 5 | |
| 2.12.0 | 1 / 5 | |
| 2.11.4 | 1 / 5 | |
| 2.11.3 | 1 / 3 | |
| 2.11.2 | 1 / 3 | |
| 2.11.1 | 1 / 3 | |
| 2.11.0 | 1 / 3 | |
| 2.10.4 | 1 / 3 | |
| 2.10.3 | 1 / 3 | |
| 2.10.2 | 1 / 3 | |
| 2.10.1 | 1 / 3 | |
| 2.10.0 | 1 / 3 | |
| 2.9.9 | 1 / 3 | |
| 2.9.8 | 1 / 3 | |
| 2.9.7 | 1 / 3 | |
| 2.9.6 | 1 / 3 | |
| 2.9.5 | 1 / 3 | |
| 2.9.4 | 1 / 3 | |
| 2.9.3 | 1 / 3 | |
| 2.9.2 | 1 / 3 | |
| 2.9.1 | 1 / 3 | |
| 2.9.0 | 1 / 3 | |
| 2.8.3 | 1 / 3 | |
| 2.8.2 | 1 / 3 | |
| 2.8.1 | 1 / 3 | |
| 2.8.0 | 1 / 3 | |
| 2.7.0 | 1 / 3 | |
| 2.6.0 | 1 / 3 | |
| 2.5.2 | 1 / 3 | |
| 2.5.1 | 1 / 3 | |
| 2.5.0 | 1 / 3 | |
| 2.4.1 | 1 / 3 | |
| 2.4.0 | 1 / 3 | |
| 2.3.3 | 1 / 3 | |
| 2.3.2 | 1 / 3 | |
| 2.3.1 | 1 / 3 | |
| 2.3.0 | 2 / 2 | |
| 2.2.11 | 2 / 2 | |
| 2.2.10 | 2 / 2 | |
| 2.2.9 | 2 / 2 | |
| 2.2.8 | 2 / 2 | |
| 2.2.7 | 2 / 2 | |
| 2.2.6 | 2 / 2 | |
| 2.2.5 | 2 / 2 | |
| 2.2.4 | 2 / 2 | |
| 2.2.3 | 2 / 2 | |
| 2.2.2 | 2 / 2 | |
| 2.2.1 | 2 / 2 | |
| 2.2.0 | 1 / 2 | |
| 2.1.10 | 1 / 2 | |
| 2.1.9 | 1 / 2 | |
| 2.1.8 | 1 / 2 | |
| 2.1.7 | 1 / 2 | |
| 2.1.6 | 1 / 2 | |
| 2.1.5 | 1 / 2 | |
| 2.1.4 | 1 / 2 | |
| 2.1.3 | 1 / 1 | |
| 2.1.2 | 1 / 1 | |
| 2.1.1 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 2.0.35 | 1 / 1 | |
| 2.0.34 | 1 / 1 | |
| 2.0.33 | 1 / 1 | |
| 2.0.32 | 1 / 1 | |
| 2.0.31 | 1 / 1 | |
| 2.0.30 | 1 / 1 | |
| 2.0.29 | 1 / 1 | |
| 2.0.28 | 1 / 1 | |
| 2.0.27 | 1 / 1 | |
| 2.0.26 | 1 / 1 | |
| 2.0.25 | 1 / 1 | |
| 2.0.24 | 1 / 1 | |
| 2.0.23 | 1 / 1 | |
| 2.0.22 | 1 / 1 | |
| 2.0.21 | 1 / 1 | |
| 2.0.20 | 1 / 1 | |
| 2.0.19 | 1 / 1 | |
| 2.0.18 | 1 / 1 | |
| 2.0.17 | 1 / 1 | |
| 2.0.16 | 1 / 1 | |
| 2.0.15 | 1 / 1 | |
| 2.0.14 | 1 / 1 | |
| 2.0.13 | 1 / 1 | |
| 2.0.12 | 1 / 1 | |
| 2.0.11 | 1 / 1 | |
| 2.0.10 | 1 / 1 | |
| 2.0.9 | 1 / 1 | |
| 2.0.8 | 1 / 1 | |
| 2.0.7 | 1 / 1 | |
| 2.0.6 | 1 / 1 |
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.