@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 — 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/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 7 of 207)
| Version | Deps | Published |
|---|---|---|
| 2.0.124 | 4 / 0 | |
| 2.0.123 | 4 / 0 | |
| 2.0.122 | 4 / 0 | |
| 2.0.121 | 4 / 0 | |
| 2.0.120 | 4 / 0 | |
| 2.0.119 | 4 / 0 | |
| 2.0.118 | 4 / 0 |
v2.0.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.