@gonkagate/hermes-agent-setup
GonkaGate onboarding helper for configuring Hermes Agent.
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Occurs in a dev/qualification script to pass env to a subprocess; not runtime credential exfiltration. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 5 / 7 | |
| 1.1.0 | 5 / 7 | |
| 1.0.0 | 5 / 7 | |
| 0.2.1 | 5 / 7 | |
| 0.2.0 | 5 / 7 | |
| 0.1.3 | 5 / 7 | |
| 0.1.0 | 5 / 7 |
v1.1.1
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.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/GonkaGate/hermes-agent-setup/blob/b8a86ad5a694167333d1dd3fb1c300c1cb299d34/scripts/launch-qualification/prepare-clean-home.mjs#L184 182 | runtime: { 183 | cwd: outputRoot, > 184 | env: { 185 | ...process.env, 186 | HERMES_HOME: hermesHomeDir,
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.