@midwayjs/consul
midway consul
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:consul | AI (dependencies): consul is the canonical npm client for HashiCorp Consul; stable dependency for this integration package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ms is a well-known, widely-trusted time utility; low risk addition for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Midwayjs monorepo component; sparse README is typical for sub-packages, not spam. | ai |
Versions (showing 38 of 138)
| Version | Deps | Published |
|---|---|---|
| 3.4.12 | 1 / 7 | |
| 3.4.11 | 1 / 7 | |
| 3.4.10 | 1 / 7 | |
| 3.4.9 | 1 / 7 | |
| 3.4.7 | 1 / 7 | |
| 3.4.6 | 1 / 7 | |
| 3.4.4 | 1 / 7 | |
| 3.4.3 | 1 / 7 | |
| 3.4.1 | 1 / 7 | |
| 3.4.0 | 1 / 7 | |
| 3.3.14 | 1 / 7 | |
| 3.3.6 | 1 / 7 | |
| 3.3.5 | 1 / 7 | |
| 3.3.4 | 1 / 7 | |
| 3.3.2 | 1 / 7 | |
| 3.3.1 | 1 / 7 | |
| 3.3.0 | 1 / 7 | |
| 3.2.2 | 1 / 7 | |
| 3.2.1 | 1 / 7 | |
| 3.2.0 | 1 / 7 | |
| 3.1.6 | 1 / 7 | |
| 3.1.5 | 1 / 7 | |
| 3.1.2 | 1 / 7 | |
| 3.1.1 | 1 / 7 | |
| 3.1.0 | 1 / 7 | |
| 3.0.13 | 1 / 7 | |
| 3.0.11 | 1 / 7 | |
| 3.0.10 | 1 / 7 | |
| 3.0.9 | 1 / 7 | |
| 3.0.8 | 1 / 7 | |
| 3.0.7 | 1 / 7 | |
| 3.0.6 | 1 / 7 | |
| 3.0.5 | 1 / 7 | |
| 3.0.4 | 1 / 7 | |
| 3.0.3 | 1 / 7 | |
| 3.0.2 | 1 / 7 | |
| 3.0.1 | 1 / 7 | |
| 3.0.0 | 1 / 7 |
v3.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.