@blocklet/discuss-kit-ux
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-lazy-with-preload | AI (phantom-deps): UI library monorepo; config-referenced deps are a stable false positive pattern for this package. | ai | |
| phantom-deps | phantom-dep:@lexical/text | AI (phantom-deps): UI library monorepo; config-referenced deps are a stable false positive pattern for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): UI library monorepo; config-referenced deps are a stable false positive pattern for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): UI library monorepo; config-referenced deps are a stable false positive pattern for this package. | ai | |
| phantom-deps | phantom-dep:url-join | AI (phantom-deps): UI library monorepo; config-referenced deps are a stable false positive pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-select | AI (phantom-deps): UI library monorepo; config-referenced deps are a stable false positive pattern for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @blocklet org's internal package publishing pattern. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire @blocklet ecosystem; not a per-version signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package from established @blocklet org; missing metadata is a pattern across all their packages. | ai |
Versions (showing 17 of 217)
| Version | Deps | Published |
|---|---|---|
| 2.3.23 | 29 / 28 | |
| 2.3.22 | 29 / 28 | |
| 2.3.21 | 29 / 28 | |
| 2.3.20 | 29 / 28 | |
| 2.3.19 | 29 / 28 | |
| 2.3.18 | 29 / 28 | |
| 2.3.17 | 29 / 28 | |
| 2.3.16 | 29 / 28 | |
| 2.3.15 | 29 / 28 | |
| 2.3.14 | 29 / 28 | |
| 2.3.12 | 29 / 28 | |
| 2.3.11 | 29 / 28 | |
| 2.3.10 | 29 / 28 | |
| 2.3.9 | 29 / 28 | |
| 2.3.8 | 29 / 28 | |
| 2.3.7 | 29 / 28 | |
| 2.3.6 | 29 / 28 |
v2.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.