@univerjs/find-replace
| Package Name | UMD Namespace | Version | License | Downloads | Contains CSS | Contains i18n locales | | --- | --- | --- | --- | --- | :---: | :---: | | `@univerjs/find-replace` | `UniverFindReplace` | [![][npm-version-shield]][npm-version-link] | ![][np
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@univerjs/icons | AI (phantom-deps): Same-org monorepo dependency; declared for version alignment, not imported directly. | ai | |
| phantom-deps | phantom-dep:@univerjs/engine-render | AI (phantom-deps): Same-org monorepo dependency; declared for version alignment, not imported directly. | ai | |
| dependencies | unvetted-dep:@univerjs/icons | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status is a pipeline artifact, not a security risk. | ai | |
| dependencies | unvetted-dep:@univerjs/ui | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status is a pipeline artifact, not a security risk. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-render | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status is a pipeline artifact, not a security risk. | ai | |
| dependencies | unvetted-dep:@univerjs/design | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status is a pipeline artifact, not a security risk. | ai | |
| dependencies | unvetted-dep:@univerjs/core | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status is a pipeline artifact, not a security risk. | ai |
Versions (showing 100 of 108)
| Version | Deps | Published |
|---|---|---|
| 0.25.1 | 5 / 7 | |
| 0.25.0 | 5 / 7 | |
| 0.24.0 | 5 / 7 | |
| 0.23.0 | 5 / 7 | |
| 0.22.1 | 5 / 7 | |
| 0.22.0 | 5 / 7 | |
| 0.21.1 | 5 / 7 | |
| 0.21.0 | 5 / 7 | |
| 0.20.1 | 5 / 7 | |
| 0.20.0 | 5 / 7 | |
| 0.19.0 | 5 / 7 | |
| 0.18.0 | 5 / 7 | |
| 0.17.0 | 5 / 8 | |
| 0.16.1 | 5 / 8 | |
| 0.16.0 | 5 / 8 | |
| 0.15.5 | 5 / 8 | |
| 0.15.4 | 5 / 8 | |
| 0.15.3 | 5 / 8 | |
| 0.15.2 | 5 / 8 | |
| 0.15.1 | 5 / 8 | |
| 0.15.0 | 5 / 8 | |
| 0.14.0 | 5 / 8 | |
| 0.13.0 | 5 / 8 | |
| 0.12.4 | 5 / 8 | |
| 0.12.3 | 5 / 8 | |
| 0.12.2 | 5 / 8 | |
| 0.12.1 | 5 / 8 | |
| 0.12.0 | 5 / 8 | |
| 0.11.0 | 5 / 8 | |
| 0.10.14 | 5 / 8 | |
| 0.10.13 | 5 / 8 | |
| 0.10.12 | 5 / 8 | |
| 0.10.11 | 5 / 8 | |
| 0.10.10 | 5 / 8 | |
| 0.10.9 | 5 / 8 | |
| 0.10.8 | 5 / 8 | |
| 0.10.7 | 5 / 8 | |
| 0.10.6 | 5 / 8 | |
| 0.10.5 | 5 / 8 | |
| 0.10.4 | 5 / 8 | |
| 0.10.3 | 5 / 8 | |
| 0.10.2 | 5 / 8 | |
| 0.10.1 | 5 / 8 | |
| 0.10.0 | 5 / 8 | |
| 0.9.4 | 5 / 8 | |
| 0.9.3 | 5 / 8 | |
| 0.9.2 | 5 / 8 | |
| 0.9.1 | 5 / 8 | |
| 0.9.0 | 5 / 8 | |
| 0.8.3 | 5 / 8 | |
| 0.8.2 | 5 / 8 | |
| 0.8.1 | 5 / 8 | |
| 0.8.0 | 5 / 8 | |
| 0.7.0 | 5 / 8 | |
| 0.6.10 | 5 / 8 | |
| 0.6.9 | 5 / 8 | |
| 0.6.8 | 5 / 8 | |
| 0.6.7 | 5 / 8 | |
| 0.6.6 | 5 / 9 | |
| 0.6.5 | 5 / 9 | |
| 0.6.4 | 5 / 9 | |
| 0.6.3 | 5 / 9 | |
| 0.6.2 | 5 / 9 | |
| 0.6.1 | 5 / 9 | |
| 0.6.0 | 5 / 9 | |
| 0.5.5 | 5 / 9 | |
| 0.5.4 | 5 / 9 | |
| 0.5.3 | 5 / 8 | |
| 0.5.2 | 5 / 9 | |
| 0.5.1 | 5 / 9 | |
| 0.5.0 | 5 / 7 | |
| 0.4.2 | 6 / 7 | |
| 0.4.1 | 6 / 7 | |
| 0.4.0 | 6 / 7 | |
| 0.3.0 | 6 / 7 | |
| 0.2.15 | 6 / 7 | |
| 0.2.14 | 6 / 7 | |
| 0.2.13 | 6 / 7 | |
| 0.2.12 | 1 / 13 | |
| 0.2.11 | 1 / 13 | |
| 0.2.10 | 1 / 13 | |
| 0.2.9 | 1 / 13 | |
| 0.2.8 | 1 / 13 | |
| 0.2.7 | 1 / 13 | |
| 0.2.6 | 1 / 13 | |
| 0.2.5 | 1 / 13 | |
| 0.2.4 | 1 / 14 | |
| 0.2.3 | 1 / 14 | |
| 0.2.2 | 1 / 14 | |
| 0.2.1 | 1 / 14 | |
| 0.2.0 | 1 / 14 | |
| 0.1.17 | 1 / 14 | |
| 0.1.16 | 1 / 14 | |
| 0.1.15 | 1 / 14 | |
| 0.1.14 | 1 / 14 | |
| 0.1.13 | 1 / 14 | |
| 0.1.12 | 1 / 14 | |
| 0.1.11 | 1 / 14 | |
| 0.1.10 | 1 / 14 | |
| 0.1.9 | 1 / 14 |
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.