@remix-run/dev
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish-env change on official Remix package; not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Manual publish is standard for this established package. | ai | |
| dependencies | unvetted-dep:@types/mdx | AI (dependencies): @types/mdx is a TypeScript type-only package with no runtime risk; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tar-fs | AI (phantom-deps): Build tool referencing deps via config conventions; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cross-spawn | AI (phantom-deps): Build tool referencing deps via config conventions; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @remix-run/dev bears no resemblance to ajv; Levenshtein match is a false positive. | ai | |
| phantom-deps | phantom-dep:@types/mdx | AI (phantom-deps): Framework-scoped type package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:gunzip-maybe | AI (phantom-deps): Build tool referencing deps via config conventions; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): Build tool referencing deps via config conventions; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:json5 | AI (phantom-deps): Build tool referencing deps via config conventions; stable false positive for this package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 2.17.5 | 56 / 28 | |
| 2.17.4 | 56 / 28 | |
| 2.17.3 | 56 / 28 | |
| 2.17.2 | 56 / 28 | |
| 2.17.1 | 56 / 28 | |
| 2.17.0 | 56 / 28 | |
| 2.16.8 | 56 / 28 | |
| 2.16.7 | 56 / 28 | |
| 2.16.6 | 56 / 28 | |
| 2.16.5 | 56 / 28 | |
| 2.16.4 | 56 / 28 | |
| 2.16.3 | 56 / 28 | |
| 2.16.2 | 56 / 28 | |
| 2.16.1 | 56 / 28 | |
| 2.16.0 | 56 / 28 | |
| 2.15.3 | 55 / 28 | |
| 2.15.2 | 55 / 28 | |
| 2.15.1 | 55 / 28 | |
| 2.15.0 | 55 / 28 | |
| 2.14.0 | 55 / 28 | |
| 2.13.1 | 53 / 28 | |
| 2.13.0 | 53 / 28 | |
| 2.12.1 | 53 / 28 | |
| 2.12.0 | 53 / 28 | |
| 2.11.2 | 53 / 28 | |
| 2.11.1 | 53 / 28 | |
| 2.11.0 | 53 / 28 | |
| 2.10.3 | 53 / 28 | |
| 2.10.2 | 53 / 28 | |
| 2.10.1 | 53 / 28 | |
| 2.10.0 | 53 / 28 | |
| 2.9.2 | 53 / 28 | |
| 2.9.1 | 53 / 28 | |
| 2.9.0 | 53 / 28 | |
| 2.8.1 | 53 / 20 | |
| 2.8.0 | 53 / 20 | |
| 2.7.2 | 53 / 20 | |
| 2.7.1 | 53 / 20 | |
| 2.7.0 | 53 / 20 | |
| 2.6.0 | 53 / 20 | |
| 2.5.1 | 53 / 19 | |
| 2.5.0 | 53 / 19 | |
| 2.4.1 | 53 / 19 | |
| 2.4.0 | 54 / 20 | |
| 2.3.1 | 56 / 20 | |
| 2.3.0 | 56 / 20 | |
| 2.2.0 | 56 / 20 | |
| 2.1.0 | 48 / 18 | |
| 2.0.1 | 48 / 18 | |
| 2.0.0 | 48 / 17 |
v2.17.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mjackson.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mjackson.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mjackson.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.