@seafile/sdoc-editor
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@seafile/seafile-database | AI (dependencies): Same-org @seafile/* dep; consistent with existing pattern of seafile-scoped dependencies in this package. | ai | |
| provenance | no-provenance | AI (provenance): Seafile org has never published with provenance; consistent across 1373 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across Seafile org packages; not indicative of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established org package with 1369 versions; missing metadata is a style issue, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@seafile/print-js | AI (phantom-deps): Same-org scoped package; likely used transitively by other @seafile deps. | ai | |
| phantom-deps | phantom-dep:@seafile/slate-hyperscript | AI (phantom-deps): Same-org scoped package; likely used transitively by other @seafile deps. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 3.0.190 | 38 / 2 | |
| 3.0.189 | 38 / 2 | |
| 3.0.188 | 38 / 2 | |
| 3.0.187 | 38 / 2 | |
| 3.0.186 | 38 / 2 | |
| 3.0.185 | 38 / 2 | |
| 3.0.184 | 38 / 2 | |
| 3.0.183 | 38 / 2 | |
| 3.0.182 | 38 / 2 | |
| 3.0.181 | 38 / 2 | |
| 3.0.180 | 38 / 2 | |
| 3.0.179 | 38 / 2 | |
| 3.0.178 | 38 / 2 | |
| 3.0.177 | 38 / 2 | |
| 3.0.176 | 38 / 2 | |
| 3.0.175 | 38 / 2 | |
| 3.0.174 | 38 / 2 | |
| 3.0.173 | 38 / 2 | |
| 3.0.172 | 38 / 2 | |
| 3.0.171 | 38 / 2 | |
| 3.0.170 | 38 / 2 | |
| 3.0.169 | 38 / 2 | |
| 3.0.168 | 38 / 2 | |
| 3.0.167 | 38 / 2 | |
| 3.0.166 | 38 / 2 | |
| 3.0.165 | 38 / 2 | |
| 3.0.164 | 38 / 2 | |
| 3.0.163 | 38 / 2 | |
| 3.0.162 | 38 / 2 | |
| 3.0.161 | 38 / 2 | |
| 3.0.160 | 38 / 2 | |
| 3.0.159 | 38 / 2 | |
| 3.0.158 | 38 / 2 | |
| 3.0.157 | 38 / 2 | |
| 3.0.156 | 38 / 2 | |
| 3.0.155 | 38 / 2 | |
| 3.0.154 | 38 / 2 | |
| 3.0.153 | 38 / 2 | |
| 3.0.152 | 38 / 2 | |
| 3.0.151 | 38 / 2 | |
| 3.0.150 | 38 / 2 | |
| 3.0.149 | 38 / 2 | |
| 3.0.148 | 38 / 2 | |
| 3.0.147 | 38 / 2 | |
| 3.0.146 | 38 / 2 | |
| 3.0.145 | 38 / 2 | |
| 3.0.143 | 38 / 2 | |
| 3.0.131 | 38 / 2 | |
| 3.0.129 | 38 / 2 | |
| 3.0.120 | 38 / 2 | |
| 3.0.109 | 38 / 2 |
v3.0.190
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.189
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.188
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.187
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.186
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.185
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.182
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.181
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.180
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.179
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.178
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.177
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.168
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.157
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.