@brendanbank/create-atrium-host
Scaffolder for new atrium host extensions: backend Python package + frontend Vite bundle + compose stack + CI, all wired against atrium's published image and host SDK packages. Run via `npx @brendanbank/create-atrium-host <name>`.
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): env spread in git.js is a standard CLI scaffolding pattern to forward committer env vars; not exfiltration. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.26.8 | 2 / 1 | |
| 0.26.7 | 2 / 1 | |
| 0.26.6 | 2 / 1 | |
| 0.26.5 | 2 / 1 | |
| 0.26.4 | 2 / 1 | |
| 0.26.3 | 2 / 1 | |
| 0.26.2 | 2 / 1 | |
| 0.26.1 | 2 / 1 | |
| 0.26.0 | 2 / 1 | |
| 0.25.4 | 2 / 1 | |
| 0.25.3 | 2 / 1 | |
| 0.25.2 | 2 / 1 | |
| 0.25.1 | 2 / 1 | |
| 0.25.0 | 2 / 1 | |
| 0.24.0 | 2 / 1 | |
| 0.23.0 | 2 / 1 | |
| 0.22.0 | 2 / 1 | |
| 0.21.0 | 2 / 1 | |
| 0.20.0 | 2 / 1 | |
| 0.19.2 | 2 / 1 | |
| 0.19.1 | 2 / 1 | |
| 0.19.0 | 2 / 1 | |
| 0.18.0 | 2 / 1 | |
| 0.17.0 | 2 / 1 | |
| 0.16.1 | 2 / 1 | |
| 0.16.0 | 2 / 1 | |
| 0.15.3 | 2 / 1 | |
| 0.15.2 | 2 / 1 | |
| 0.15.1 | 2 / 1 | |
| 0.15.0 | 2 / 1 |
v0.26.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.5
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.4
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.3
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.2
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.1
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.4
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.3
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.2
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.1
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.2
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.1
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.1
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.3
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.2
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.1
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | await run('git', ['commit', '-n', '--no-gpg-sign', '-m', 'Initial scaffold'], { 45 | cwd, > 46 | env: { ...process.env, GIT_COMMITTER_NAME: process.env.GIT_COMMITTER_NAME ?? process.env.USER ?? 'scaffold', GIT_COM 47 | }); 48 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.