@shoplflow/templates
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@shoplflow/utils | AI (phantom-deps): Internal org dependency; re-exported or used in config. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer dep referenced in config; stable pattern for this component library. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): Component library config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:simplebar-react | AI (phantom-deps): Component library config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-datepicker | AI (phantom-deps): Component library config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Component library; deps referenced in config/re-exports, not direct imports. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react | AI (phantom-deps): Component library config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react-dom | AI (phantom-deps): Component library config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@shoplflow/hada-assets | AI (phantom-deps): Same-org sibling package; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/core | AI (phantom-deps): Component library config reference; stable false positive for this package. | ai |
Versions (showing 69 of 169)
| Version | Deps | Published |
|---|---|---|
| 0.1.17 | 16 / 42 | |
| 0.1.16 | 16 / 42 | |
| 0.1.15 | 16 / 42 | |
| 0.1.14 | 16 / 42 | |
| 0.1.13 | 16 / 42 | |
| 0.1.12 | 16 / 42 | |
| 0.1.11 | 16 / 42 | |
| 0.1.10 | 16 / 42 | |
| 0.1.9 | 16 / 42 | |
| 0.1.8 | 16 / 42 | |
| 0.1.7 | 16 / 42 | |
| 0.1.6 | 16 / 42 | |
| 0.1.5 | 16 / 42 | |
| 0.1.4 | 16 / 42 | |
| 0.1.3 | 16 / 42 | |
| 0.1.2 | 16 / 42 | |
| 0.1.1 | 16 / 42 | |
| 0.1.0 | 16 / 42 | |
| 0.0.55 | 13 / 41 | |
| 0.0.54 | 13 / 41 | |
| 0.0.53 | 13 / 41 | |
| 0.0.52 | 13 / 41 | |
| 0.0.51 | 13 / 41 | |
| 0.0.50 | 13 / 41 | |
| 0.0.49 | 13 / 41 | |
| 0.0.48 | 13 / 41 | |
| 0.0.47 | 13 / 41 | |
| 0.0.46 | 13 / 41 | |
| 0.0.45 | 13 / 41 | |
| 0.0.44 | 13 / 41 | |
| 0.0.43 | 13 / 41 | |
| 0.0.42 | 13 / 41 | |
| 0.0.41 | 13 / 41 | |
| 0.0.40 | 13 / 41 | |
| 0.0.39 | 13 / 41 | |
| 0.0.38 | 13 / 41 | |
| 0.0.37 | 13 / 41 | |
| 0.0.36 | 13 / 41 | |
| 0.0.35 | 13 / 41 | |
| 0.0.34 | 13 / 41 | |
| 0.0.33 | 13 / 41 | |
| 0.0.32 | 13 / 41 | |
| 0.0.31 | 13 / 41 | |
| 0.0.30 | 13 / 41 | |
| 0.0.29 | 13 / 41 | |
| 0.0.28 | 13 / 41 | |
| 0.0.27 | 13 / 41 | |
| 0.0.26 | 13 / 41 | |
| 0.0.25 | 13 / 41 | |
| 0.0.24 | 13 / 41 | |
| 0.0.23 | 13 / 41 | |
| 0.0.22 | 13 / 41 | |
| 0.0.21 | 13 / 41 | |
| 0.0.19 | 13 / 41 | |
| 0.0.18 | 13 / 41 | |
| 0.0.17 | 13 / 41 | |
| 0.0.16 | 13 / 41 | |
| 0.0.14 | 13 / 41 | |
| 0.0.13 | 13 / 41 | |
| 0.0.12 | 13 / 41 | |
| 0.0.11 | 13 / 41 | |
| 0.0.10 | 13 / 41 | |
| 0.0.9 | 13 / 41 | |
| 0.0.8 | 13 / 41 | |
| 0.0.7 | 13 / 41 | |
| 0.0.6 | 13 / 41 | |
| 0.0.5 | 13 / 41 | |
| 0.0.4 | 13 / 41 | |
| 0.0.3 | 13 / 41 |
v0.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.