← Home

@remix-run/cli

npm Repository Homepage

Command-line interface for Remix

7
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

mjackson

Keywords

remixcliscaffoldprojectcommand-line

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Explicit placeholder/namespace-reservation package; 0.0.0 is intentional per package.json description. ai
bogus-package bogus-package AI (bogus-package): Intentional CI/OIDC placeholder; tiny payload and no deps are expected for a namespace reservation. ai
semgrep semgrep:env-spread AI (semgrep): Used in a worker-env builder that copies then filters process.env; not exfiltration, stable pattern for this package. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get used to access a named export from a dynamic route module; legitimate pattern, not obfuscation. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @remix-run namespace; Levenshtein match against 'joi' is a false positive. ai

Versions (showing 7 of 7)

Version Deps Published
0.3.3 3 / 4
0.3.2 3 / 4
0.3.1 3 / 4
0.3.0 3 / 4
0.2.0 3 / 4
0.1.0 4 / 4
0.0.0 0 / 0

v0.3.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.0

2 findings
HIGH env-spread: src/lib/route-map.ts:294 semgrep

Spreading entire process.env into an object — may capture all secrets 292 | 293 | function createRouteMapWorkerEnv(): NodeJS.ProcessEnv { > 294 | let env = { ...process.env } 295 | 296 | for (let key of Object.keys(env)) {

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.0

2 findings
HIGH env-spread: src/lib/route-map.ts:294 semgrep

Spreading entire process.env into an object — may capture all secrets 292 | 293 | function createRouteMapWorkerEnv(): NodeJS.ProcessEnv { > 294 | let env = { ...process.env } 295 | 296 | for (let key of Object.keys(env)) {

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.0

1 finding
LOW No provenance attestation provenance

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