@haklex/rich-compose
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are same-org @haklex/* siblings at matching version; monorepo consolidation pattern, not supply-chain injection. | ai | |
| phantom-deps | phantom-dep:@haklex/rich-litexml | AI (phantom-deps): @haklex/rich-litexml is a same-org monorepo sibling declared as a dep; phantom-dep is a false positive here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 20 / 14 | |
| 0.18.0 | 20 / 14 | |
| 0.17.1 | 20 / 14 | |
| 0.16.1 | 20 / 14 | |
| 0.16.0 | 20 / 14 | |
| 0.15.9 | 20 / 14 | |
| 0.15.7 | 20 / 14 | |
| 0.15.6 | 20 / 14 | |
| 0.15.5 | 20 / 14 | |
| 0.15.4 | 20 / 14 | |
| 0.15.3 | 20 / 14 | |
| 0.15.2 | 20 / 14 | |
| 0.15.1 | 20 / 14 | |
| 0.15.0 | 20 / 14 | |
| 0.14.1 | 20 / 14 | |
| 0.14.0 | 20 / 14 | |
| 0.13.0 | 20 / 14 | |
| 0.12.0 | 20 / 14 | |
| 0.11.0 | 20 / 14 | |
| 0.10.0 | 20 / 14 | |
| 0.9.3 | 19 / 14 | |
| 0.9.2 | 19 / 14 | |
| 0.9.1 | 19 / 14 | |
| 0.9.0 | 19 / 14 | |
| 0.8.0 | 19 / 14 | |
| 0.7.0 | 19 / 14 | |
| 0.6.2 | 19 / 14 | |
| 0.6.1 | 1 / 31 | |
| 0.6.0 | 1 / 31 | |
| 0.5.0 | 0 / 28 | |
| 0.2.0 | 0 / 27 | |
| 0.1.0 | 0 / 18 |
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.