@haklex/rich-ext-code-snippet
Multi-file code snippet extension
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:@haklex/rich-renderer-codeblock | AI (phantom-deps): Same-org scoped package; likely re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@iconify/utils | AI (phantom-deps): Transitive dependency; typical for icon/styling libraries. | ai | |
| phantom-deps | phantom-dep:@iconify-json/material-icon-theme | AI (phantom-deps): Transitive dependency; typical for icon/styling libraries. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): Transitive dependency; typical for UI component libraries. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/sortable | AI (phantom-deps): Transitive dependency; typical for UI component libraries. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/utilities | AI (phantom-deps): Transitive dependency; typical for UI component libraries. | ai | |
| phantom-deps | phantom-dep:shiki | AI (phantom-deps): shiki is a declared runtime dep; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai |
Versions (showing 51 of 143)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 9 / 13 | |
| 0.18.0 | 10 / 12 | |
| 0.17.1 | 10 / 12 | |
| 0.16.1 | 10 / 12 | |
| 0.16.0 | 10 / 12 | |
| 0.15.9 | 10 / 12 | |
| 0.15.7 | 10 / 12 | |
| 0.15.6 | 10 / 12 | |
| 0.15.5 | 10 / 12 | |
| 0.15.4 | 10 / 12 | |
| 0.15.2 | 10 / 12 | |
| 0.15.1 | 10 / 12 | |
| 0.15.0 | 10 / 12 | |
| 0.14.1 | 10 / 12 | |
| 0.14.0 | 10 / 12 | |
| 0.13.0 | 10 / 12 | |
| 0.12.0 | 10 / 12 | |
| 0.11.0 | 10 / 12 | |
| 0.10.0 | 10 / 12 | |
| 0.9.3 | 10 / 12 | |
| 0.9.2 | 10 / 12 | |
| 0.9.1 | 10 / 12 | |
| 0.9.0 | 10 / 12 | |
| 0.8.0 | 10 / 12 | |
| 0.7.0 | 10 / 12 | |
| 0.6.2 | 10 / 12 | |
| 0.6.1 | 10 / 12 | |
| 0.6.0 | 10 / 12 | |
| 0.5.0 | 10 / 12 | |
| 0.4.1 | 10 / 12 | |
| 0.4.0 | 10 / 12 | |
| 0.3.4 | 10 / 12 | |
| 0.3.3 | 10 / 12 | |
| 0.3.2 | 10 / 12 | |
| 0.3.1 | 10 / 12 | |
| 0.3.0 | 13 / 12 | |
| 0.2.0 | 13 / 12 | |
| 0.1.1 | 13 / 12 | |
| 0.1.0 | 13 / 12 | |
| 0.0.110 | 13 / 12 | |
| 0.0.109 | 13 / 12 | |
| 0.0.108 | 13 / 12 | |
| 0.0.107 | 13 / 12 | |
| 0.0.106 | 14 / 12 | |
| 0.0.105 | 14 / 12 | |
| 0.0.104 | 14 / 12 | |
| 0.0.103 | 14 / 12 | |
| 0.0.102 | 14 / 12 | |
| 0.0.101 | 14 / 12 | |
| 0.0.100 | 14 / 12 | |
| 0.0.99 | 14 / 12 |
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.