@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 51 of 204)
| Version | Deps | Published |
|---|---|---|
| 2.6.25 | 34 / 22 | |
| 2.6.18 | 34 / 22 | |
| 2.6.13 | 34 / 22 | |
| 2.6.11 | 34 / 22 | |
| 2.6.10 | 34 / 22 | |
| 2.5.76 | 34 / 22 | |
| 2.5.27 | 34 / 22 | |
| 2.5.25 | 34 / 22 | |
| 2.5.12 | 34 / 22 | |
| 2.5.9 | 34 / 22 | |
| 2.5.2 | 34 / 22 | |
| 2.5.1 | 34 / 22 | |
| 2.5.0 | 34 / 22 | |
| 2.4.126 | 34 / 22 | |
| 2.4.125 | 34 / 22 | |
| 2.4.124 | 34 / 22 | |
| 2.4.123 | 34 / 22 | |
| 2.4.122 | 34 / 22 | |
| 2.4.121 | 34 / 22 | |
| 2.4.120 | 34 / 22 | |
| 2.4.119 | 34 / 22 | |
| 2.4.118 | 34 / 22 | |
| 2.4.117 | 34 / 22 | |
| 2.4.116 | 34 / 22 | |
| 2.4.115 | 34 / 22 | |
| 2.4.114 | 34 / 22 | |
| 2.4.112 | 34 / 22 | |
| 2.4.111 | 34 / 22 | |
| 2.4.110 | 34 / 22 | |
| 2.4.109 | 34 / 22 | |
| 2.4.108 | 34 / 22 | |
| 2.4.107 | 34 / 22 | |
| 2.4.106 | 34 / 22 | |
| 2.4.105 | 34 / 22 | |
| 2.4.104 | 34 / 22 | |
| 2.4.103 | 34 / 22 | |
| 2.4.102 | 34 / 22 | |
| 2.4.101 | 34 / 22 | |
| 2.4.100 | 34 / 22 | |
| 2.4.99 | 34 / 22 | |
| 2.4.98 | 34 / 22 | |
| 2.4.97 | 34 / 22 | |
| 2.4.96 | 34 / 22 | |
| 2.4.95 | 34 / 22 | |
| 2.4.94 | 34 / 22 | |
| 2.4.93 | 34 / 22 | |
| 2.4.92 | 34 / 22 | |
| 2.4.91 | 34 / 22 | |
| 2.4.90 | 34 / 22 | |
| 2.4.89 | 34 / 22 | |
| 2.4.88 | 34 / 22 |
v2.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.