dtable-ui-component
[document](https://seatable.github.io/dtable-ui-component/docs/)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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 Seafile org package; no provenance is consistent across all 799 versions. | ai | |
| dependencies | unvetted-dep:rmc-tabs | AI (dependencies): rmc-tabs is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:rmc-dialog | AI (dependencies): rmc-dialog is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:rmc-drawer | AI (dependencies): rmc-drawer is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:rmc-picker | AI (dependencies): rmc-picker is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:rmc-tooltip | AI (dependencies): rmc-tooltip is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:rmc-cascader | AI (dependencies): rmc-cascader is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:rmc-date-picker | AI (dependencies): rmc-date-picker is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:rmc-notification | AI (dependencies): rmc-notification is a known Ant Design Mobile component; stable dep for this UI library. | ai | |
| dependencies | unvetted-dep:dtable-utils | AI (dependencies): dtable-utils is the same Seafile org's utility package; expected dep for this UI library. | ai | |
| dependencies | unvetted-dep:react-sweet-progress | AI (dependencies): react-sweet-progress is a well-known progress bar component; stable dep for this UI library. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 6.0.124 | 23 / 73 | |
| 6.0.123 | 23 / 73 | |
| 6.0.122 | 23 / 73 | |
| 6.0.121 | 23 / 73 | |
| 6.0.120 | 23 / 73 | |
| 6.0.119 | 23 / 73 | |
| 6.0.118 | 23 / 73 | |
| 6.0.117 | 23 / 73 | |
| 6.0.116 | 23 / 73 | |
| 6.0.115 | 23 / 73 | |
| 6.0.114 | 23 / 73 | |
| 6.0.113 | 23 / 73 | |
| 6.0.112 | 23 / 73 | |
| 6.0.111 | 23 / 73 | |
| 6.0.110 | 23 / 73 | |
| 6.0.109 | 23 / 74 | |
| 6.0.108 | 23 / 74 | |
| 6.0.107 | 23 / 74 | |
| 6.0.106 | 23 / 74 | |
| 6.0.105 | 23 / 74 | |
| 6.0.104 | 23 / 75 | |
| 6.0.103 | 23 / 75 | |
| 6.0.102 | 23 / 76 | |
| 6.0.101 | 23 / 76 | |
| 6.0.100 | 23 / 76 | |
| 6.0.99 | 23 / 76 | |
| 6.0.98 | 23 / 76 | |
| 6.0.97 | 23 / 76 | |
| 6.0.96 | 23 / 76 | |
| 6.0.95 | 23 / 76 | |
| 6.0.94 | 23 / 76 | |
| 6.0.93 | 23 / 76 | |
| 6.0.92 | 23 / 76 | |
| 6.0.91 | 23 / 92 | |
| 6.0.89 | 23 / 92 | |
| 6.0.88 | 23 / 92 | |
| 6.0.55 | 23 / 76 | |
| 6.0.54 | 23 / 92 | |
| 6.0.53 | 23 / 92 | |
| 6.0.52 | 23 / 92 | |
| 6.0.51 | 23 / 92 | |
| 6.0.50 | 23 / 92 | |
| 6.0.49 | 23 / 92 | |
| 6.0.48 | 23 / 92 | |
| 6.0.47 | 23 / 92 | |
| 6.0.46 | 23 / 92 | |
| 6.0.45 | 23 / 92 | |
| 6.0.44 | 23 / 92 | |
| 6.0.43 | 23 / 92 | |
| 6.0.42 | 23 / 92 | |
| 6.0.41 | 23 / 92 |
v6.0.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.