@getmikk/core
> AST parsing, dependency graph, Merkle hashing, contract management, boundary enforcement, risk analysis.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @getmikk/core is part of the mikk project; not a typosquat of cors. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decode is inside a security scanner that inspects strings for obfuscation; not executing decoded content. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Same security scanner context as base64-decode; decoding for analysis, not execution. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.1.5 | 9 / 4 | |
| 2.1.4 | 9 / 4 | |
| 2.1.3 | 9 / 4 | |
| 2.1.2 | 6 / 4 | |
| 2.1.1 | 6 / 4 | |
| 2.1.0 | 6 / 4 | |
| 2.0.18 | 6 / 4 | |
| 2.0.17 | 6 / 4 | |
| 2.0.16 | 6 / 4 | |
| 2.0.15 | 6 / 4 | |
| 2.0.14 | 5 / 4 | |
| 2.0.13 | 5 / 4 | |
| 2.0.12 | 5 / 4 | |
| 2.0.11 | 5 / 4 | |
| 2.0.10 | 6 / 2 | |
| 2.0.0 | 9 / 2 | |
| 1.9.1 | 9 / 2 | |
| 1.9.0 | 8 / 3 | |
| 1.8.3 | 6 / 3 | |
| 1.8.2 | 6 / 3 | |
| 1.8.1 | 6 / 3 | |
| 1.8.0 | 6 / 3 | |
| 1.7.1 | 4 / 3 | |
| 1.7.0 | 4 / 3 | |
| 1.6.0 | 4 / 3 | |
| 1.5.1 | 4 / 2 | |
| 1.5.0 | 4 / 2 | |
| 1.3.2 | 4 / 2 | |
| 1.3.1 | 4 / 2 | |
| 1.3.0 | 4 / 2 |
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.