@hg-ts/config-loader
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal framework package; missing description is consistent across all versions of this monorepo. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 214 versions; stable pattern for this private monorepo package. | ai |
Versions (showing 51 of 163)
| Version | Deps | Published |
|---|---|---|
| 0.7.27 | 1 / 17 | |
| 0.7.26 | 1 / 17 | |
| 0.7.25 | 1 / 17 | |
| 0.7.24 | 1 / 17 | |
| 0.7.23 | 1 / 17 | |
| 0.7.22 | 1 / 17 | |
| 0.7.21 | 1 / 17 | |
| 0.7.20 | 1 / 17 | |
| 0.7.19 | 1 / 17 | |
| 0.7.18 | 1 / 17 | |
| 0.7.17 | 1 / 17 | |
| 0.7.16 | 1 / 17 | |
| 0.7.15 | 1 / 17 | |
| 0.7.14 | 1 / 17 | |
| 0.7.13 | 1 / 17 | |
| 0.7.12 | 1 / 17 | |
| 0.7.11 | 1 / 17 | |
| 0.7.10 | 1 / 17 | |
| 0.7.9 | 1 / 17 | |
| 0.7.8 | 1 / 17 | |
| 0.7.7 | 1 / 17 | |
| 0.7.6 | 1 / 17 | |
| 0.7.5 | 1 / 17 | |
| 0.7.4 | 1 / 17 | |
| 0.7.3 | 1 / 17 | |
| 0.7.2 | 1 / 17 | |
| 0.5.40 | 1 / 17 | |
| 0.5.39 | 1 / 17 | |
| 0.5.38 | 1 / 17 | |
| 0.5.37 | 1 / 17 | |
| 0.5.36 | 1 / 17 | |
| 0.5.35 | 1 / 17 | |
| 0.5.34 | 1 / 17 | |
| 0.5.32 | 1 / 17 | |
| 0.5.31 | 1 / 17 | |
| 0.5.30 | 1 / 17 | |
| 0.5.29 | 1 / 17 | |
| 0.5.28 | 1 / 17 | |
| 0.5.27 | 1 / 17 | |
| 0.5.26 | 1 / 17 | |
| 0.5.25 | 1 / 17 | |
| 0.5.24 | 1 / 17 | |
| 0.5.23 | 1 / 17 | |
| 0.5.22 | 1 / 17 | |
| 0.5.21 | 1 / 17 | |
| 0.5.20 | 1 / 17 | |
| 0.5.19 | 1 / 17 | |
| 0.5.18 | 1 / 17 | |
| 0.5.17 | 1 / 17 | |
| 0.5.16 | 1 / 17 | |
| 0.5.15 | 1 / 17 |
v0.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.