@seafile/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/sdoc-editor | AI (dependencies): Same-org dependency (@seafile/sdoc-editor) consistent with this package's role as a wrapper; stable pattern across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description; consistent across all @seafile/seafile-sdoc-editor versions. | ai | |
| provenance | no-provenance | AI (provenance): Seafile org does not use Sigstore provenance; stable pattern across 310 versions. | ai |
Versions (showing 51 of 230)
| Version | Deps | Published |
|---|---|---|
| 3.0.223 | 4 / 0 | |
| 3.0.222 | 4 / 0 | |
| 3.0.221 | 4 / 0 | |
| 3.0.220 | 4 / 0 | |
| 3.0.219 | 4 / 0 | |
| 3.0.218 | 4 / 0 | |
| 3.0.217 | 4 / 0 | |
| 3.0.216 | 4 / 0 | |
| 3.0.215 | 4 / 0 | |
| 3.0.214 | 4 / 0 | |
| 3.0.213 | 4 / 0 | |
| 3.0.212 | 4 / 0 | |
| 3.0.211 | 4 / 0 | |
| 3.0.210 | 4 / 0 | |
| 3.0.209 | 4 / 0 | |
| 3.0.208 | 4 / 0 | |
| 3.0.207 | 4 / 0 | |
| 3.0.206 | 4 / 0 | |
| 3.0.205 | 4 / 0 | |
| 3.0.204 | 4 / 0 | |
| 3.0.203 | 4 / 0 | |
| 3.0.202 | 4 / 0 | |
| 3.0.201 | 4 / 0 | |
| 3.0.200 | 4 / 0 | |
| 3.0.199 | 4 / 0 | |
| 3.0.198 | 4 / 0 | |
| 3.0.197 | 4 / 0 | |
| 3.0.196 | 4 / 0 | |
| 3.0.194 | 4 / 0 | |
| 3.0.193 | 4 / 0 | |
| 3.0.192 | 4 / 0 | |
| 3.0.191 | 4 / 0 | |
| 3.0.190 | 4 / 0 | |
| 3.0.189 | 4 / 0 | |
| 3.0.188 | 4 / 0 | |
| 3.0.187 | 4 / 0 | |
| 3.0.186 | 4 / 0 | |
| 3.0.185 | 4 / 0 | |
| 3.0.184 | 4 / 0 | |
| 3.0.183 | 4 / 0 | |
| 3.0.182 | 4 / 0 | |
| 3.0.181 | 4 / 0 | |
| 3.0.180 | 4 / 0 | |
| 3.0.179 | 4 / 0 | |
| 3.0.178 | 4 / 0 | |
| 3.0.177 | 4 / 0 | |
| 3.0.176 | 4 / 0 | |
| 3.0.175 | 4 / 0 | |
| 3.0.174 | 4 / 0 | |
| 3.0.173 | 4 / 0 | |
| 3.0.172 | 4 / 0 |
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.