@univerjs/sheets-numfmt
UniverSheet numfmt plugin
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@univerjs/engine-numfmt | AI (dependencies): Same-org monorepo sibling; consistently approved across the univerjs ecosystem. | ai | |
| dependencies | unvetted-dep:@univerjs/core | AI (dependencies): Internal sibling dep from same monorepo; version-pinned and expected. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets | AI (dependencies): Internal sibling dep from same monorepo; version-pinned and expected. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-formula | AI (dependencies): Internal sibling dep from same monorepo; version-pinned and expected. | ai |
Versions (showing 8 of 108)
| Version | Deps | Published |
|---|---|---|
| 0.1.8 | 1 / 17 | |
| 0.1.7 | 1 / 17 | |
| 0.1.6 | 1 / 17 | |
| 0.1.5 | 1 / 17 | |
| 0.1.4 | 1 / 17 | |
| 0.1.3 | 1 / 17 | |
| 0.1.2 | 1 / 17 | |
| 0.1.1 | 1 / 17 |
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.