oclif

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/c13f6490b4f5f3a8053a6d8ff1314535cb70cc75/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/bcd537a7b704eab783ff59f5be0c87d8e20d5247/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/feaf3dfbdce8611cc8ed911003d1e555a31befba/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/2c6b4acb602c00be901bb304f36bfd845f3cdb1b/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/8d4ebb53d0693bf8aba298e367f495825378d91b/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/106d5c16dee8fe2d0161a1fd5573f1a076583c71/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/8662699ccdade7259e5e6f974aae7f320fbd70c5/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/c0293c0e9a0ca8cc0f85c29d1a500ffa3e3a877f/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/48c10e607693d5a6ec639a41af87ee7fa30badab/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/9c41ca986dd7a392da318931a96ff2d8a2aad31a/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/4dbd6e68fd7c5aaecee44f9e01c7ecc441e1102a/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/b185670e554ded55735b2aeb1b01b76e0d15dd2b/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/4c7923d5c3e466f96f2b0844a9d3201d8f10a8e8/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/1dc10f64e4df01f614c7e8fe3eb0bb30bfa6da1d/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/5a68ab15f21a8e3f448be31e8e11027000a478a0/lib/commands/generate.js#L240 238 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 239 | // in that scenario. > 240 | env: { ...process.env, NODE_ENV: 'production' }, 241 | silent: false, 242 | });

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/oclif/blob/32f881a382305bde4a8215f73264909f43772700/lib/generators/cli.js#L44 42 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to production 43 | // in that scenario. > 44 | env: { ...process.env, NODE_ENV: 'production' }, 45 | }); 46 | console.log(`\nCreated ${this.pjson.name} in ${this.destinationRoot()}`);

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.