@doist/ui-extensions-server
This package contains all the shared elements for all the extensions within this repository.
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:typeorm-encrypted | AI (dependencies): Pinned dependency fitting the ORM encryption use case; stable for this package. | ai | |
| dependencies | unvetted-dep:date-time-format-timezone | AI (dependencies): Pinned timezone utility dependency; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Doist org internal server library; sparse README/no keywords is expected for a scoped enterprise package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.5.7 | 7 / 0 | |
| 3.5.6 | 7 / 0 | |
| 3.5.4 | 7 / 0 | |
| 3.5.3 | 7 / 0 | |
| 3.5.2 | 7 / 0 | |
| 3.5.1 | 7 / 0 | |
| 3.5.0 | 7 / 0 | |
| 3.4.1 | 7 / 0 | |
| 3.4.0 | 8 / 0 |
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.