@shoplflow/base
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed by SLSA provenance attestation; stable CI/CD pattern for this package. | ai | |
| dependencies | unvetted-dep:@figma/code-connect | AI (dependencies): Official Figma tooling package matching the figma:parse/publish scripts added in this version. | ai | |
| phantom-deps | phantom-dep:@figma/code-connect | AI (phantom-deps): @figma/code-connect is used via CLI (npx figma connect) in scripts, not direct import; phantom-dep is a stable false positive here. | ai |
Versions (showing 100 of 219)
| Version | Deps | Published |
|---|---|---|
| 0.41.2 | 13 / 41 | |
| 0.41.1 | 13 / 41 | |
| 0.41.0 | 13 / 41 | |
| 0.40.7 | 13 / 41 | |
| 0.40.6 | 13 / 41 | |
| 0.40.5 | 13 / 41 | |
| 0.40.4 | 13 / 41 | |
| 0.40.3 | 13 / 41 | |
| 0.40.2 | 13 / 41 | |
| 0.40.1 | 13 / 41 | |
| 0.40.0 | 13 / 41 | |
| 0.39.2 | 13 / 41 | |
| 0.39.1 | 13 / 41 | |
| 0.39.0 | 13 / 41 | |
| 0.38.1 | 13 / 41 | |
| 0.38.0 | 13 / 41 | |
| 0.37.6 | 13 / 41 | |
| 0.37.5 | 13 / 41 | |
| 0.37.4 | 13 / 41 | |
| 0.37.3 | 13 / 41 | |
| 0.37.2 | 13 / 41 | |
| 0.37.1 | 13 / 41 | |
| 0.37.0 | 13 / 41 | |
| 0.36.1 | 13 / 41 | |
| 0.36.0 | 13 / 41 | |
| 0.35.1 | 13 / 41 | |
| 0.35.0 | 13 / 41 | |
| 0.34.0 | 13 / 41 | |
| 0.33.4 | 13 / 41 | |
| 0.33.3 | 13 / 41 | |
| 0.33.2 | 13 / 41 | |
| 0.33.1 | 13 / 41 | |
| 0.33.0 | 13 / 41 | |
| 0.32.47 | 13 / 41 | |
| 0.32.46 | 13 / 41 | |
| 0.32.45 | 13 / 41 | |
| 0.32.44 | 13 / 41 | |
| 0.32.43 | 13 / 41 | |
| 0.32.42 | 13 / 41 | |
| 0.32.41 | 13 / 41 | |
| 0.32.40 | 13 / 41 | |
| 0.32.39 | 13 / 41 | |
| 0.32.38 | 13 / 41 | |
| 0.32.37 | 13 / 41 | |
| 0.32.36 | 13 / 41 | |
| 0.32.35 | 13 / 41 | |
| 0.32.34 | 13 / 41 | |
| 0.32.33 | 13 / 41 | |
| 0.32.32 | 13 / 41 | |
| 0.32.31 | 13 / 41 | |
| 0.32.30 | 13 / 41 | |
| 0.32.29 | 13 / 41 | |
| 0.32.28 | 13 / 41 | |
| 0.32.27 | 13 / 41 | |
| 0.32.26 | 13 / 41 | |
| 0.32.25 | 13 / 41 | |
| 0.32.24 | 13 / 41 | |
| 0.32.23 | 13 / 41 | |
| 0.32.22 | 13 / 40 | |
| 0.32.21 | 13 / 40 | |
| 0.32.20 | 13 / 40 | |
| 0.32.19 | 13 / 40 | |
| 0.32.18 | 13 / 40 | |
| 0.32.17 | 13 / 40 | |
| 0.32.16 | 13 / 40 | |
| 0.32.15 | 13 / 40 | |
| 0.32.14 | 13 / 40 | |
| 0.32.13 | 13 / 40 | |
| 0.32.12 | 11 / 42 | |
| 0.32.11 | 11 / 42 | |
| 0.32.10 | 11 / 42 | |
| 0.32.9 | 11 / 42 | |
| 0.32.8 | 11 / 42 | |
| 0.32.6 | 11 / 42 | |
| 0.32.5 | 11 / 42 | |
| 0.32.4 | 11 / 42 | |
| 0.32.3 | 11 / 42 | |
| 0.32.2 | 11 / 42 | |
| 0.32.1 | 11 / 42 | |
| 0.32.0 | 11 / 42 | |
| 0.31.21 | 11 / 42 | |
| 0.31.20 | 11 / 42 | |
| 0.31.19 | 11 / 42 | |
| 0.31.18 | 11 / 42 | |
| 0.31.17 | 11 / 42 | |
| 0.31.16 | 11 / 42 | |
| 0.31.15 | 11 / 42 | |
| 0.31.14 | 11 / 42 | |
| 0.31.13 | 11 / 42 | |
| 0.31.12 | 11 / 42 | |
| 0.31.11 | 11 / 42 | |
| 0.31.10 | 11 / 42 | |
| 0.31.9 | 11 / 42 | |
| 0.31.8 | 8 / 42 | |
| 0.31.7 | 8 / 42 | |
| 0.31.6 | 8 / 42 | |
| 0.31.5 | 8 / 42 | |
| 0.31.4 | 8 / 42 | |
| 0.31.3 | 8 / 42 | |
| 0.31.2 | 8 / 42 |
v0.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.