@diia-inhouse/healthcheck
Healthcheck
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
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 2.1.25 | 3 / 27 | |
| 2.1.24 | 3 / 27 | |
| 2.1.23 | 3 / 27 | |
| 2.1.22 | 3 / 27 | |
| 2.1.21 | 3 / 27 | |
| 2.1.20 | 3 / 27 | |
| 2.1.19 | 3 / 27 | |
| 2.1.18 | 3 / 27 | |
| 2.1.17 | 3 / 27 | |
| 2.1.16 | 3 / 27 | |
| 2.1.15 | 3 / 27 | |
| 2.1.14 | 3 / 27 | |
| 2.1.13 | 3 / 27 | |
| 2.1.12 | 3 / 27 | |
| 2.1.11 | 3 / 27 | |
| 2.1.10 | 3 / 27 | |
| 2.1.9 | 3 / 27 | |
| 2.1.8 | 3 / 27 | |
| 2.1.7 | 3 / 27 | |
| 2.1.6 | 3 / 27 | |
| 1.18.10 | 3 / 24 | |
| 1.18.9 | 3 / 24 | |
| 1.18.8 | 3 / 24 | |
| 1.18.7 | 3 / 24 | |
| 1.18.6 | 3 / 24 | |
| 1.18.5 | 3 / 24 | |
| 1.18.4 | 3 / 24 | |
| 1.18.3 | 3 / 24 | |
| 1.18.2 | 3 / 24 | |
| 1.18.1 | 3 / 24 | |
| 1.18.0 | 3 / 24 | |
| 1.17.19 | 3 / 24 | |
| 1.17.13 | 3 / 24 | |
| 1.17.12 | 3 / 24 | |
| 1.17.11 | 3 / 24 | |
| 1.17.10 | 3 / 24 | |
| 1.17.9 | 3 / 24 | |
| 1.17.8 | 3 / 24 | |
| 1.17.7 | 3 / 24 | |
| 1.17.6 | 3 / 24 | |
| 1.17.5 | 3 / 24 | |
| 1.17.4 | 3 / 24 | |
| 1.17.3 | 3 / 24 | |
| 1.17.2 | 3 / 24 | |
| 1.17.1 | 3 / 24 | |
| 1.17.0 | 3 / 24 | |
| 1.16.1 | 3 / 24 |
v2.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.