oclif

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

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/52ed6d11f9389162cf055f272e3b27e3dfcefab8/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/86027e08736cda0c3d47fec3ff68ac08b59b1438/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/62400a793e193d6b2a68a4af890bc653c8fabd2e/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/8d7fc88bc85bd86dcc1c8978bdbe5e03db201523/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/6ea10947f80b0a264b14baa15f2945cc70c9369d/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/9d9c29ad3c2b03eb0170399fb1095fb5b3c2d352/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/35cac185b9401ee640490b23fcb799290ee7e888/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/a10a70cb4000f723ea27e76fd4eb8cf62240bd25/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/36ce1e4f4669e271b05c3221f6eb459555478950/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/220155aab4413aa7ab51150341784756abf6c891/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/d1709f81683ee2ce7c054fdb9cacfd5ae95401bf/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/22a5a4178fcabaea77ddf49661cc20a892a8cbf4/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/7614199e5ad291baea90f0efe5c289a754f7aa2f/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/61828030f5ed01d82bad0f3701f31be18d296565/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/a7984068f63fa5bee47d26ad4d4ee0e3579b8502/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/e5b9c5529bf91ce9fc38eae469f218558948eb8b/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/83cb53c09a9520592cecd8a5146db1fb8b5ac251/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/85e5ee2116b83436fdc585c33744484f4d4b9c94/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/f1398b37b508b5d5def75d0fae880ff03d4f8faa/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/c277a8f111c1597989665a02fffd067509b4e8f7/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/2e2c0ad3daca19b3457163ad5d587ce0dc2cc2f2/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/d325e3f57ed54ee9e18596be9a39cdefc9a89986/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/0011a1211cd2fc27ba674bad2d93173ca441436e/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/a74383c08358a20c609bd4f7349a651d671524d6/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/5a1b2536665602ab0e97d21db32432fa12feb40e/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/fc4a60a693706a25b4e92a7e4fb14733fef6dba8/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/b84f7d9266677645d860df9327e13aadb75a1a3d/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/8db10034197079f60a952471599397932d302a23/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/56548b3fbcd0c8f86ea2f0356c586d6b99ace418/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/d8d27e7bd7bab022b180191b4d3966aa12bfd33e/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/c4fe85407f7ac88f43ef07bea2b0084c114e91de/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/595ad1637a2d8664cfff2f95ff1ffc5f95f29e15/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/21d5d412034a9df9558840f6b7d14ba630df2e99/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/4615e054d6a0786f34257573f4f37c471244218a/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/28f02b7f22fd534cbf2e7c3261a3409245d54e62/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/9f364c6e215aff35a9133b17640c93ef6ba163f4/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/38214bf8e2c2bbc2992dd1d124ec01308d117a6d/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/91e359bcf58f9e0190c41a320564e30ea1f2fc1d/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/32c310ed5763476fa787bc2f9fdec434e1f312f3/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/aa45d97c054034cda66a920d959c3922a1ca4c3a/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/4eadb2ee8243a5d109f0b7acfb4531223c994285/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/929887885775211fd59a2e2553f7b25d72c69997/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/8174ae1a0c9f63a22c6ac60fe8bfe26016cf5c76/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/e37712f726ed36b08080a35ccc61ff8bbb44e9a0/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/d360e0122a4e61193d7005ced515bae845b90742/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/54065c68b19cd842bfbdeb7ee0ac8884975fb0a8/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/4abc123baffb9ac342f0eeea221d749881c97c3f/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/b3cd26a86ce0704035daed6f887cd8e277d5ff24/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/307978e110114bfce56c9334dbbcc35f9f655762/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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/176e93ae77901839cd685ef7aeee6de9844f0b49/lib/commands/generate.js#L241 239 | // doesn't affect the behavior of the command in production since the NODE_ENV is already set to product 240 | // in that scenario. > 241 | env: { ...process.env, NODE_ENV: 'production' }, 242 | silent: false, 243 | });

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