@lhx-kit/tsconfig
Shared TypeScript configuration presets for the lhx-kit monorepo (base/library/react/vue/node). Designed so packages can `extends` via Node resolution — works identically before AND after npm publish.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): Package publishes via CI/CD with Sigstore attestation; this is the expected publish pattern for this monorepo. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual (luhanxin) to GitHub Actions publishing is consistent with CI/CD adoption; SLSA attestation confirms integrity. | ai | |
| provenance | missing-githead | AI (provenance): gitHead absence is expected when publishing via GitHub Actions CI; SLSA attestation provides equivalent commit traceability. | ai |
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-05-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-05-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.