@vtex/cli-plugin-workspace
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:vtex-latest | AI (dependencies): Alias for official vtex package (npm:[email protected]), not a separate untrusted package. | ai | |
| npm-metadata | url-dep:nodemon-notifier-cli | AI (npm-metadata): Dev-only dependency not included in published files; no runtime risk. | ai | |
| phantom-deps | phantom-dep:@oclif/config | AI (phantom-deps): @oclif/config is a declared runtime dep used via oclif config files, not direct imports; stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 7 / 19 | |
| 1.1.6 | 4 / 19 | |
| 1.1.5 | 9 / 18 | |
| 1.1.4 | 4 / 19 | |
| 1.1.3 | 5 / 20 | |
| 1.1.2 | 5 / 21 | |
| 1.1.1 | 4 / 21 | |
| 1.1.0 | 4 / 21 |
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.