metro-resolver
🚇 Implementation of Metro's resolution logic.
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.84.4 | 1 / 1 | |
| 0.84.3 | 1 / 1 | |
| 0.84.2 | 1 / 1 | |
| 0.84.1 | 1 / 1 | |
| 0.84.0 | 1 / 1 | |
| 0.83.7 | 1 / 1 | |
| 0.83.6 | 1 / 1 | |
| 0.83.5 | 1 / 1 | |
| 0.83.4 | 1 / 1 | |
| 0.83.3 | 1 / 1 | |
| 0.83.2 | 1 / 1 | |
| 0.83.1 | 1 / 1 | |
| 0.83.0 | 1 / 1 | |
| 0.82.5 | 1 / 1 | |
| 0.82.4 | 1 / 1 | |
| 0.82.3 | 1 / 1 | |
| 0.82.2 | 1 / 1 | |
| 0.81.5 | 1 / 1 |
v0.84.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.