@midwayjs/bootstrap
midwayjs bootstrap
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:@midwayjs/event-bus | AI (dependencies): Official first-party @midwayjs scoped package, not unvetted. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org sibling package, benign. | ai |
Versions (showing 5 of 105)
| Version | Deps | Published |
|---|---|---|
| 3.0.5 | 0 / 8 | |
| 3.0.4 | 0 / 8 | |
| 3.0.2 | 0 / 8 | |
| 3.0.1 | 0 / 8 | |
| 3.0.0 | 0 / 8 |
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.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.