@stonecrop/atable
Advanced data table component for Stonecrop
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/stores/table.js | AI (source-diff): Standard Pinia/Vue store; no actual network calls or dynamic code execution in the sample. | ai | |
| source-diff | net-exec-file:dist/atable.umd.cjs | AI (source-diff): Sample shows standard Vue/Pinia UMD bundle with Google Fonts CSS import; no actual network-fetched code execution. | ai | |
| source-diff | net-exec-file:dist/src/stores/table.js | AI (source-diff): Sample shows legitimate Pinia store implementation with no network calls or dynamic code execution visible. | ai | |
| phantom-deps | phantom-dep:@stonecrop/themes | AI (phantom-deps): Same-org monorepo sibling; indirect consumption is expected in this build setup. | ai | |
| phantom-deps | phantom-dep:@stonecrop/utilities | AI (phantom-deps): Same-org monorepo sibling; indirect consumption is expected in this build setup. | ai | |
| phantom-deps | phantom-dep:@vueuse/components | AI (phantom-deps): Referenced in config files per finding; not a true phantom dep for this package. | ai |
Versions (showing 84 of 184)
| Version | Deps | Published |
|---|---|---|
| 0.4.16 | 6 / 19 | |
| 0.4.15 | 6 / 19 | |
| 0.4.14 | 6 / 19 | |
| 0.4.13 | 6 / 19 | |
| 0.4.12 | 6 / 19 | |
| 0.4.11 | 6 / 19 | |
| 0.4.10 | 6 / 19 | |
| 0.4.9 | 6 / 19 | |
| 0.4.8 | 6 / 19 | |
| 0.4.7 | 6 / 19 | |
| 0.4.6 | 6 / 19 | |
| 0.4.5 | 6 / 19 | |
| 0.4.4 | 6 / 19 | |
| 0.4.3 | 6 / 19 | |
| 0.4.2 | 6 / 19 | |
| 0.4.1 | 6 / 19 | |
| 0.4.0 | 6 / 19 | |
| 0.3.11 | 6 / 19 | |
| 0.3.10 | 6 / 19 | |
| 0.3.9 | 6 / 19 | |
| 0.3.8 | 6 / 19 | |
| 0.3.7 | 6 / 19 | |
| 0.3.6 | 6 / 19 | |
| 0.3.5 | 6 / 19 | |
| 0.3.4 | 6 / 19 | |
| 0.3.3 | 6 / 19 | |
| 0.3.2 | 6 / 19 | |
| 0.3.1 | 6 / 19 | |
| 0.3.0 | 6 / 19 | |
| 0.2.67 | 6 / 19 | |
| 0.2.66 | 6 / 19 | |
| 0.2.65 | 6 / 19 | |
| 0.2.64 | 6 / 19 | |
| 0.2.63 | 5 / 19 | |
| 0.2.62 | 5 / 19 | |
| 0.2.61 | 5 / 19 | |
| 0.2.60 | 5 / 19 | |
| 0.2.59 | 5 / 19 | |
| 0.2.58 | 5 / 19 | |
| 0.2.57 | 5 / 19 | |
| 0.2.56 | 5 / 19 | |
| 0.2.55 | 5 / 19 | |
| 0.2.54 | 5 / 19 | |
| 0.2.53 | 5 / 19 | |
| 0.2.52 | 5 / 19 | |
| 0.2.51 | 5 / 19 | |
| 0.2.50 | 5 / 19 | |
| 0.2.49 | 5 / 19 | |
| 0.2.48 | 5 / 18 | |
| 0.2.47 | 5 / 18 | |
| 0.2.46 | 5 / 18 | |
| 0.2.45 | 5 / 18 | |
| 0.2.44 | 5 / 18 | |
| 0.2.43 | 6 / 19 | |
| 0.2.42 | 6 / 19 | |
| 0.2.41 | 6 / 19 | |
| 0.2.40 | 6 / 19 | |
| 0.2.39 | 6 / 19 | |
| 0.2.38 | 6 / 19 | |
| 0.2.37 | 6 / 19 | |
| 0.2.36 | 6 / 19 | |
| 0.2.35 | 6 / 19 | |
| 0.2.34 | 6 / 19 | |
| 0.2.33 | 6 / 19 | |
| 0.2.32 | 6 / 19 | |
| 0.2.31 | 6 / 19 | |
| 0.2.30 | 6 / 19 | |
| 0.2.29 | 6 / 19 | |
| 0.2.28 | 6 / 19 | |
| 0.2.27 | 6 / 19 | |
| 0.2.26 | 6 / 19 | |
| 0.2.25 | 6 / 19 | |
| 0.2.24 | 4 / 21 | |
| 0.2.23 | 4 / 21 | |
| 0.2.22 | 4 / 21 | |
| 0.2.21 | 4 / 21 | |
| 0.2.20 | 4 / 21 | |
| 0.2.18 | 4 / 21 | |
| 0.2.17 | 4 / 21 | |
| 0.2.16 | 4 / 19 | |
| 0.2.13 | 4 / 19 | |
| 0.2.11 | 4 / 19 | |
| 0.2.10 | 4 / 19 | |
| 0.2.9 | 4 / 19 |
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.