@vue-storefront/middleware
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Integration loader pattern; resolves user-configured modules by name from cwd — expected for a middleware framework. | ai | |
| phantom-deps | phantom-dep:@types/multer | AI (phantom-deps): @types/multer is a type dependency listed in runtime deps for type augmentation; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.4.1 | 10 / 6 | |
| 5.4.0 | 10 / 6 | |
| 5.3.2 | 10 / 6 | |
| 5.3.1 | 10 / 6 | |
| 5.3.0 | 10 / 6 | |
| 5.2.0 | 10 / 6 | |
| 5.1.1 | 8 / 6 | |
| 5.1.0 | 8 / 6 | |
| 5.0.1 | 7 / 6 | |
| 5.0.0 | 6 / 6 |
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.