@jskit-ai/crud-server-generator
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Code generator intentionally spreads process.env into template context; pattern is stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect generator scaffold template files, not a spam/malicious package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal generator tool; missing description is cosmetic, not a risk signal here. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.1.93 | 8 / 0 | |
| 0.1.92 | 8 / 0 | |
| 0.1.91 | 8 / 0 | |
| 0.1.90 | 8 / 0 | |
| 0.1.88 | 8 / 0 | |
| 0.1.87 | 8 / 0 | |
| 0.1.86 | 8 / 0 | |
| 0.1.85 | 8 / 0 | |
| 0.1.84 | 8 / 0 | |
| 0.1.83 | 8 / 0 | |
| 0.1.82 | 8 / 0 | |
| 0.1.81 | 8 / 0 | |
| 0.1.80 | 8 / 0 | |
| 0.1.79 | 8 / 0 | |
| 0.1.78 | 8 / 0 | |
| 0.1.77 | 8 / 0 | |
| 0.1.76 | 8 / 0 | |
| 0.1.75 | 8 / 0 | |
| 0.1.74 | 8 / 0 | |
| 0.1.73 | 8 / 0 | |
| 0.1.72 | 8 / 0 | |
| 0.1.71 | 8 / 0 | |
| 0.1.70 | 8 / 0 | |
| 0.1.69 | 8 / 0 | |
| 0.1.68 | 8 / 0 | |
| 0.1.67 | 8 / 0 | |
| 0.1.66 | 8 / 0 | |
| 0.1.65 | 8 / 0 | |
| 0.1.64 | 8 / 0 | |
| 0.1.63 | 8 / 0 | |
| 0.1.62 | 8 / 0 | |
| 0.1.61 | 8 / 0 | |
| 0.1.60 | 8 / 0 | |
| 0.1.59 | 8 / 0 | |
| 0.1.58 | 8 / 0 | |
| 0.1.57 | 8 / 0 | |
| 0.1.56 | 8 / 0 | |
| 0.1.55 | 8 / 0 | |
| 0.1.54 | 8 / 0 | |
| 0.1.53 | 8 / 0 | |
| 0.1.52 | 8 / 0 | |
| 0.1.51 | 8 / 0 | |
| 0.1.50 | 8 / 0 | |
| 0.1.49 | 8 / 0 | |
| 0.1.48 | 8 / 0 | |
| 0.1.47 | 8 / 0 | |
| 0.1.46 | 8 / 0 | |
| 0.1.45 | 8 / 0 | |
| 0.1.44 | 8 / 0 | |
| 0.1.43 | 8 / 0 | |
| 0.1.42 | 8 / 0 |
v0.1.93
2 findingsSpreading entire process.env into an object — may capture all secrets 213 | } 214 | > 215 | return { 216 | ...parsed, 217 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.92
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.91
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.90
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.88
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.87
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.86
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.85
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.84
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.83
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.82
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.81
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.80
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.79
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.78
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.77
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.76
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.75
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.74
2 findingsSpreading entire process.env into an object — may capture all secrets 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
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 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
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 210 | } 211 | > 212 | return { 213 | ...parsed, 214 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
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 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
2 findingsSpreading entire process.env into an object — may capture all secrets 196 | } 197 | > 198 | return { 199 | ...parsed, 200 | ...process.env
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.