@jskit-ai/create-app
Scaffold minimal JSKIT app shells.
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
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): Pattern is in a server-side runtimeEnv helper; spreading process.env is a known design choice, not malicious exfiltration. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.1.93 | 0 / 0 | |
| 0.1.92 | 0 / 0 | |
| 0.1.91 | 0 / 0 | |
| 0.1.90 | 0 / 0 | |
| 0.1.89 | 0 / 0 | |
| 0.1.88 | 0 / 0 | |
| 0.1.87 | 0 / 0 | |
| 0.1.86 | 0 / 0 | |
| 0.1.85 | 0 / 0 | |
| 0.1.84 | 0 / 0 | |
| 0.1.83 | 0 / 0 | |
| 0.1.82 | 0 / 0 | |
| 0.1.81 | 0 / 0 | |
| 0.1.80 | 0 / 0 | |
| 0.1.79 | 0 / 0 | |
| 0.1.78 | 0 / 0 | |
| 0.1.77 | 0 / 0 | |
| 0.1.76 | 0 / 0 | |
| 0.1.75 | 0 / 0 | |
| 0.1.74 | 0 / 0 | |
| 0.1.73 | 0 / 0 | |
| 0.1.72 | 0 / 0 | |
| 0.1.71 | 0 / 0 | |
| 0.1.70 | 0 / 0 | |
| 0.1.69 | 0 / 0 | |
| 0.1.68 | 0 / 0 | |
| 0.1.67 | 0 / 0 | |
| 0.1.66 | 0 / 0 | |
| 0.1.65 | 0 / 0 | |
| 0.1.64 | 0 / 0 | |
| 0.1.63 | 0 / 0 | |
| 0.1.62 | 0 / 0 | |
| 0.1.61 | 0 / 0 | |
| 0.1.60 | 0 / 0 | |
| 0.1.59 | 0 / 0 | |
| 0.1.58 | 0 / 0 | |
| 0.1.57 | 0 / 0 | |
| 0.1.56 | 0 / 0 | |
| 0.1.55 | 0 / 0 | |
| 0.1.54 | 0 / 0 | |
| 0.1.53 | 0 / 0 | |
| 0.1.52 | 0 / 0 | |
| 0.1.51 | 0 / 0 | |
| 0.1.50 | 0 / 0 | |
| 0.1.49 | 0 / 0 | |
| 0.1.48 | 0 / 0 | |
| 0.1.47 | 0 / 0 | |
| 0.1.46 | 0 / 0 | |
| 0.1.45 | 0 / 0 | |
| 0.1.44 | 0 / 0 | |
| 0.1.43 | 0 / 0 |
v0.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.74
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.73
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.72
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.71
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.70
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.69
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.68
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.67
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.66
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.65
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.64
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.63
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.62
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.61
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.60
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.59
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.58
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.57
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.56
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.55
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.54
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.53
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.52
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.51
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.50
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.49
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.48
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
2 findingsSpreading entire process.env into an object — may capture all secrets 35 | process.env.JSKIT_SERVER_SURFACE || process.env.SERVER_SURFACE 36 | ); > 37 | return { 38 | ...process.env, 39 | SERVER_SURFACE: serverSurface,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.