← Home

@univerjs/preset-sheets-filter

npm Repository Homepage
71
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jikkaiwbfsamengshukeji

Keywords

univeruniver-presetsheetsfilter

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Established org package; missing description is a cosmetic issue, not a risk indicator. ai
provenance no-provenance AI (provenance): DreamNum publishes the entire @univerjs ecosystem without provenance; consistent across versions. ai

Versions (showing 71 of 71)

Version Deps Published
0.25.1 2 / 6
0.25.0 2 / 6
0.24.0 2 / 6
0.23.0 2 / 6
0.22.1 2 / 6
0.22.0 2 / 6
0.21.1 2 / 6
0.21.0 2 / 6
0.20.1 2 / 6
0.20.0 2 / 6
0.19.0 2 / 6
0.18.0 2 / 6
0.17.0 2 / 6
0.16.1 2 / 6
0.16.0 2 / 6
0.15.5 2 / 6
0.15.4 2 / 6
0.15.3 2 / 6
0.15.2 2 / 6
0.15.1 2 / 6
0.15.0 2 / 6
0.14.0 2 / 6
0.13.0 2 / 6
0.12.4 2 / 6
0.12.3 2 / 6
0.12.2 2 / 6
0.12.1 2 / 6
0.12.0 2 / 6
0.11.0 2 / 6
0.10.14 2 / 6
0.10.13 2 / 6
0.10.12 2 / 6
0.10.11 2 / 6
0.10.10 2 / 6
0.10.9 2 / 6
0.10.8 2 / 6
0.10.7 2 / 6
0.10.6 2 / 6
0.10.5 2 / 6
0.10.4 2 / 6
0.10.3 2 / 6
0.10.2 2 / 6
0.10.1 2 / 6
0.10.0 2 / 6
0.9.4 2 / 6
0.9.3 2 / 6
0.9.2 2 / 6
0.9.1 2 / 6
0.9.0 2 / 6
0.8.3 2 / 6
0.8.2 2 / 6
0.8.1 2 / 6
0.8.0 2 / 6
0.7.0 2 / 6
0.6.10 2 / 5
0.6.9 2 / 5
0.6.8 2 / 5
0.6.7 2 / 5
0.6.6 2 / 5
0.6.5 2 / 3
0.6.4 2 / 3
0.6.3 2 / 3
0.6.2 2 / 3
0.6.1 2 / 3
0.6.0 2 / 3
0.5.5 2 / 3
0.5.4 2 / 3
0.5.3 2 / 3
0.5.2 2 / 3
0.5.1 2 / 3
0.5.0 2 / 3

v0.6.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.