bare-module-resolve
Low-level module resolution algorithm for Bare
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.12.4 | 1 / 5 | |
| 1.12.3 | 1 / 5 | |
| 1.12.2 | 1 / 5 | |
| 1.12.1 | 1 / 4 | |
| 1.12.0 | 1 / 4 | |
| 1.11.3 | 1 / 4 | |
| 1.11.2 | 1 / 4 | |
| 1.11.1 | 1 / 4 | |
| 1.11.0 | 1 / 4 | |
| 1.10.2 | 1 / 4 | |
| 1.10.1 | 1 / 4 | |
| 1.10.0 | 1 / 3 | |
| 1.9.0 | 1 / 3 | |
| 1.8.2 | 1 / 2 | |
| 1.8.1 | 1 / 2 | |
| 1.8.0 | 1 / 2 | |
| 1.7.3 | 1 / 2 | |
| 1.7.2 | 1 / 2 | |
| 1.7.1 | 1 / 2 | |
| 1.7.0 | 1 / 2 | |
| 1.6.2 | 1 / 2 | |
| 1.6.1 | 1 / 2 | |
| 1.6.0 | 1 / 2 | |
| 1.5.1 | 0 / 2 | |
| 1.5.0 | 0 / 2 | |
| 1.4.4 | 0 / 2 | |
| 1.4.3 | 0 / 2 | |
| 1.4.2 | 0 / 2 | |
| 1.4.1 | 0 / 2 | |
| 1.3.1 | 0 / 2 | |
| 1.3.0 | 0 / 2 | |
| 1.2.6 | 0 / 2 | |
| 1.2.5 | 0 / 2 | |
| 1.2.4 | 0 / 2 | |
| 1.2.3 | 0 / 2 | |
| 1.2.2 | 0 / 2 | |
| 1.2.1 | 0 / 2 | |
| 1.2.0 | 0 / 2 | |
| 1.1.0 | 0 / 2 | |
| 1.0.1 | 0 / 2 | |
| 1.0.0 | 0 / 2 |
v1.12.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.