@haklex/rich-renderers
Static renderers aggregator for haklex rich editor
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:@haklex/rich-ext-tldraw | AI (dependencies): Same @haklex namespace as this package; part of the same rich editor ecosystem, not a suspicious external dependency. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @haklex packages; not a per-version risk signal. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 14 / 10 | |
| 0.3.4 | 13 / 9 | |
| 0.3.3 | 13 / 9 | |
| 0.3.2 | 13 / 9 | |
| 0.3.1 | 13 / 9 | |
| 0.3.0 | 14 / 9 | |
| 0.2.0 | 14 / 9 | |
| 0.1.1 | 14 / 9 | |
| 0.1.0 | 14 / 9 | |
| 0.0.110 | 14 / 9 | |
| 0.0.109 | 14 / 9 | |
| 0.0.108 | 14 / 9 | |
| 0.0.107 | 14 / 9 | |
| 0.0.106 | 14 / 9 | |
| 0.0.105 | 14 / 9 | |
| 0.0.104 | 14 / 9 | |
| 0.0.103 | 14 / 9 | |
| 0.0.102 | 14 / 9 | |
| 0.0.101 | 14 / 9 | |
| 0.0.100 | 14 / 9 | |
| 0.0.99 | 14 / 9 | |
| 0.0.98 | 14 / 9 | |
| 0.0.97 | 14 / 9 | |
| 0.0.95 | 14 / 9 | |
| 0.0.94 | 14 / 9 | |
| 0.0.93 | 14 / 9 | |
| 0.0.92 | 14 / 9 | |
| 0.0.91 | 14 / 9 | |
| 0.0.90 | 14 / 9 | |
| 0.0.89 | 14 / 9 | |
| 0.0.88 | 14 / 9 | |
| 0.0.87 | 14 / 9 | |
| 0.0.86 | 14 / 9 | |
| 0.0.85 | 14 / 9 | |
| 0.0.84 | 14 / 9 | |
| 0.0.83 | 14 / 9 | |
| 0.0.82 | 14 / 9 | |
| 0.0.81 | 14 / 9 | |
| 0.0.80 | 14 / 9 | |
| 0.0.79 | 14 / 9 | |
| 0.0.78 | 14 / 9 | |
| 0.0.77 | 14 / 9 | |
| 0.0.76 | 14 / 9 | |
| 0.0.75 | 14 / 9 | |
| 0.0.74 | 14 / 9 | |
| 0.0.73 | 14 / 9 | |
| 0.0.72 | 14 / 9 | |
| 0.0.71 | 14 / 9 | |
| 0.0.70 | 14 / 9 | |
| 0.0.68 | 14 / 9 | |
| 0.0.67 | 14 / 9 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.