@univerjs/uniscript
UI component library for building exceptional Univer.
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/design | AI (phantom-deps): Same-org dependency; transitive usage in monorepo is stable pattern. | ai | |
| phantom-deps | phantom-dep:@univerjs/sheets | AI (phantom-deps): Same-org dependency; transitive usage in monorepo is stable pattern. | ai | |
| phantom-deps | phantom-dep:@univerjs/sheets-ui | AI (phantom-deps): Same-org dependency; transitive usage in monorepo is stable pattern. | ai | |
| dependencies | unvetted-dep:@univerjs/design | AI (dependencies): Same-monorepo sibling dep at matching version. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Intentional design: this package is a scripting engine that executes user code via new Function(); not a malware indicator. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-ui | AI (dependencies): Same-monorepo sibling dep at matching version. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets | AI (dependencies): Same-monorepo sibling dep at matching version. | ai | |
| dependencies | unvetted-dep:@univerjs/ui | AI (dependencies): Same-monorepo sibling dep at matching version; expected pattern for @univerjs/* packages. | ai | |
| dependencies | unvetted-dep:@univerjs/core | AI (dependencies): Same-monorepo sibling dep at matching version. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.25.0 | 6 / 7 | |
| 0.24.0 | 6 / 7 | |
| 0.23.0 | 6 / 7 | |
| 0.22.1 | 6 / 7 | |
| 0.22.0 | 6 / 7 | |
| 0.21.1 | 6 / 7 | |
| 0.21.0 | 6 / 7 | |
| 0.20.1 | 6 / 7 | |
| 0.20.0 | 6 / 7 | |
| 0.19.0 | 6 / 7 | |
| 0.18.0 | 6 / 7 | |
| 0.17.0 | 6 / 8 | |
| 0.16.1 | 6 / 8 | |
| 0.16.0 | 6 / 8 | |
| 0.15.5 | 6 / 8 | |
| 0.15.4 | 6 / 8 | |
| 0.15.3 | 6 / 8 | |
| 0.15.2 | 6 / 8 | |
| 0.15.1 | 6 / 8 | |
| 0.15.0 | 6 / 8 | |
| 0.14.0 | 6 / 8 | |
| 0.13.0 | 6 / 8 | |
| 0.12.4 | 6 / 8 | |
| 0.12.3 | 6 / 8 | |
| 0.12.2 | 6 / 8 | |
| 0.12.1 | 6 / 8 | |
| 0.12.0 | 6 / 8 | |
| 0.11.0 | 6 / 8 | |
| 0.10.14 | 6 / 8 | |
| 0.10.13 | 6 / 8 | |
| 0.10.12 | 6 / 8 | |
| 0.10.11 | 6 / 8 | |
| 0.10.10 | 6 / 8 | |
| 0.10.9 | 6 / 8 | |
| 0.10.8 | 6 / 8 | |
| 0.10.7 | 6 / 8 | |
| 0.10.6 | 6 / 8 | |
| 0.10.5 | 6 / 8 | |
| 0.10.4 | 6 / 8 | |
| 0.10.3 | 6 / 8 | |
| 0.10.2 | 6 / 8 | |
| 0.10.1 | 6 / 8 | |
| 0.10.0 | 6 / 8 | |
| 0.9.4 | 6 / 8 | |
| 0.9.3 | 6 / 8 | |
| 0.9.2 | 6 / 8 | |
| 0.9.1 | 6 / 8 | |
| 0.9.0 | 6 / 8 | |
| 0.8.3 | 6 / 8 | |
| 0.8.2 | 6 / 8 | |
| 0.8.1 | 6 / 8 | |
| 0.8.0 | 6 / 8 | |
| 0.7.0 | 6 / 8 |
v0.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.