@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, so a manually published version cannot be tied back to a reviewed commit.
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 90)
| Version | Deps | Published |
|---|---|---|
| 3.0.223 | 38 / 2 | |
| 3.0.222 | 38 / 2 | |
| 3.0.221 | 38 / 2 | |
| 3.0.220 | 38 / 2 | |
| 3.0.219 | 38 / 2 | |
| 3.0.218 | 38 / 2 | |
| 3.0.217 | 38 / 2 | |
| 3.0.216 | 38 / 2 | |
| 3.0.215 | 38 / 2 | |
| 3.0.214 | 38 / 2 | |
| 3.0.213 | 38 / 2 | |
| 3.0.212 | 38 / 2 | |
| 3.0.211 | 38 / 2 | |
| 3.0.210 | 38 / 2 | |
| 3.0.209 | 38 / 2 | |
| 3.0.208 | 38 / 2 | |
| 3.0.207 | 38 / 2 | |
| 3.0.206 | 38 / 2 | |
| 3.0.205 | 38 / 2 | |
| 3.0.204 | 38 / 2 | |
| 3.0.203 | 38 / 2 | |
| 3.0.202 | 38 / 2 | |
| 3.0.201 | 38 / 2 | |
| 3.0.200 | 38 / 2 | |
| 3.0.199 | 38 / 2 | |
| 3.0.198 | 38 / 2 | |
| 3.0.197 | 38 / 2 | |
| 3.0.196 | 38 / 2 | |
| 3.0.194 | 38 / 2 | |
| 3.0.193 | 38 / 2 | |
| 3.0.192 | 38 / 2 | |
| 3.0.191 | 38 / 2 | |
| 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 |
v3.0.223
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.222
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.221
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.220
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.219
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.218
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.217
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.216
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.215
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.214
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.213
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.212
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.211
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.210
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.