@geekmidas/cli
CLI tools for building Lambda handlers, server applications, and generating OpenAPI specs
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@geekmidas/manifest | AI (dependencies): First-party @geekmidas org package, same monorepo family as other deps. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package, not a supply-chain risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads package.json by filesystem path; not arbitrary user-controlled module loading. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires in encryption test suite validating base64 output; no payload hiding. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Fires in encryption utility decoding AES key/IV from hex; standard crypto pattern. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Pattern is child-process spawn with NODE_OPTIONS injection; not credential exfiltration. | ai | |
| phantom-deps | phantom-dep:openapi-typescript | AI (phantom-deps): Listed as runtime dep; used via config/CLI invocation rather than direct import. | ai | |
| phantom-deps | phantom-dep:@apidevtools/swagger-parser | AI (phantom-deps): Listed as runtime dep; used via config/CLI invocation rather than direct import. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @geekmidas/cli is a scoped CLI tool; levenshtein match to 'joi' is coincidental. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Fires only in test fixtures using 127.0.0.1 localhost addresses. | ai |
Versions (showing 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 1.12.0 | 23 / 8 | |
| 1.11.0 | 22 / 8 | |
| 1.10.41 | 22 / 8 | |
| 1.10.40 | 22 / 8 | |
| 1.10.39 | 22 / 8 | |
| 1.10.38 | 22 / 8 | |
| 1.10.37 | 22 / 8 | |
| 1.10.36 | 22 / 8 | |
| 1.10.35 | 22 / 8 | |
| 1.10.34 | 22 / 8 | |
| 1.10.33 | 22 / 8 | |
| 1.10.32 | 22 / 8 | |
| 1.10.31 | 22 / 8 | |
| 1.10.30 | 22 / 8 | |
| 1.10.29 | 22 / 8 | |
| 1.10.28 | 22 / 8 | |
| 1.10.27 | 22 / 8 | |
| 1.10.26 | 22 / 8 | |
| 1.10.25 | 22 / 8 | |
| 1.10.24 | 22 / 8 | |
| 1.10.23 | 22 / 8 | |
| 1.10.22 | 22 / 8 | |
| 1.10.21 | 22 / 8 | |
| 1.10.20 | 22 / 8 | |
| 1.10.19 | 22 / 8 | |
| 1.10.18 | 22 / 8 | |
| 1.10.17 | 22 / 8 | |
| 1.10.16 | 22 / 8 | |
| 1.10.15 | 22 / 8 | |
| 1.10.14 | 22 / 8 | |
| 1.10.13 | 22 / 8 | |
| 1.10.12 | 22 / 8 | |
| 1.10.11 | 22 / 8 | |
| 1.10.10 | 22 / 8 | |
| 1.10.9 | 22 / 8 | |
| 1.10.8 | 22 / 8 | |
| 1.10.7 | 22 / 8 | |
| 1.10.6 | 22 / 8 | |
| 1.10.5 | 22 / 8 | |
| 1.10.4 | 22 / 8 | |
| 1.10.3 | 22 / 8 | |
| 1.10.2 | 22 / 8 | |
| 1.10.1 | 22 / 8 | |
| 1.10.0 | 22 / 8 | |
| 1.9.1 | 22 / 8 | |
| 1.9.0 | 22 / 8 | |
| 1.8.0 | 22 / 8 | |
| 1.7.0 | 22 / 8 | |
| 1.6.0 | 22 / 8 | |
| 1.5.1 | 21 / 8 | |
| 1.5.0 | 19 / 8 | |
| 1.4.0 | 19 / 8 | |
| 1.3.0 | 19 / 8 | |
| 1.2.3 | 19 / 8 | |
| 1.2.2 | 19 / 8 | |
| 1.2.1 | 19 / 8 | |
| 1.2.0 | 19 / 8 | |
| 1.1.0 | 19 / 8 | |
| 1.0.2 | 19 / 8 | |
| 1.0.1 | 19 / 8 | |
| 1.0.0 | 19 / 8 | |
| 0.54.0 | 15 / 8 | |
| 0.53.0 | 15 / 8 | |
| 0.52.0 | 15 / 8 | |
| 0.49.0 | 15 / 8 | |
| 0.48.0 | 14 / 7 | |
| 0.46.0 | 14 / 7 | |
| 0.44.0 | 14 / 7 | |
| 0.42.0 | 14 / 7 | |
| 0.41.0 | 14 / 7 | |
| 0.39.0 | 14 / 7 | |
| 0.38.0 | 14 / 7 | |
| 0.37.0 | 14 / 7 | |
| 0.36.0 | 14 / 7 | |
| 0.35.0 | 14 / 7 | |
| 0.34.0 | 14 / 7 | |
| 0.31.0 | 14 / 7 | |
| 0.30.0 | 14 / 7 | |
| 0.29.0 | 14 / 7 | |
| 0.28.0 | 14 / 7 | |
| 0.27.0 | 14 / 7 | |
| 0.26.0 | 14 / 7 | |
| 0.25.0 | 14 / 7 | |
| 0.24.0 | 14 / 7 | |
| 0.23.0 | 14 / 7 | |
| 0.21.0 | 8 / 7 | |
| 0.20.0 | 8 / 7 | |
| 0.19.0 | 8 / 7 | |
| 0.18.0 | 8 / 7 | |
| 0.17.0 | 8 / 7 | |
| 0.16.0 | 8 / 7 | |
| 0.15.0 | 8 / 7 | |
| 0.14.0 | 8 / 7 | |
| 0.13.0 | 8 / 7 | |
| 0.12.0 | 8 / 7 | |
| 0.10.0 | 8 / 7 | |
| 0.9.0 | 8 / 7 | |
| 0.8.0 | 8 / 7 | |
| 0.7.0 | 8 / 7 | |
| 0.6.2 | 8 / 7 |
v1.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (geekmidas) on 2026-01-18, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (geekmidas) on 2026-01-18, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.