← Home

@vtex/cli-plugin-content

npm Repository Homepage

vtex plugin content

24
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

eduardoformiganatamelorafarubimvictorhmplurianarturpimentelemersonlaurentinoviniagostinilucasaarcoverdelariciamotageraldo.fernandesmateuspontesvitorlgomesmarcelovicentegcmaianabthiagolcmwendermendescamarathiago.pereira.vtexkevinvtexmyllena.alvesenzomercajardelymarisdaniyelnnrdenissilvavtexvinhagsgeorgebrindeiromarcos_vtexlaisribeirolucasfp13-vtexbrunoamuifdaciuk_vtexsophreisvtexsagginvtexwilliamcunhavtexamandascmvtexgabriel_bozellithaynannunesvtexlab-useryasmintelesguieevc-vtexevertonstrackarthurtriis1vtexmmartinsolivrerissonvtexernestosbarbosawisney.cardealgabriellymourampcardosorafael.pereiraamilton.vtexoremluis.mafraluis.mollmannleidymgdevguilhermeribeiro30

Keywords

oclif-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:nodemon-notifier-cli AI (npm-metadata): Dev-only tooling dependency, not shipped or executed at install time. ai
maintainer-change maintainer-added AI (maintainer-change): VTEX-suffixed accounts replacing departed team members, consistent with org rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): Part of same routine team rotation, no takeover behavior observed. ai
phantom-deps phantom-dep:@oclif/config AI (phantom-deps): Used indirectly via oclif config, common false positive. ai

Versions (showing 24 of 24)

Version Deps Published
1.10.1 10 / 19
1.10.0 10 / 19
1.9.0 10 / 19
1.8.1 10 / 19
1.7.2 10 / 19
1.7.1 10 / 19
1.7.0 10 / 19
1.6.0 10 / 19
1.5.0 10 / 19
1.4.1 10 / 19
1.4.0 10 / 19
1.3.2 10 / 19
1.3.0 9 / 19
1.2.0 9 / 19
1.1.2 8 / 19
1.1.1 8 / 19
1.1.0 8 / 19
1.0.6 8 / 19
1.0.5 8 / 19
1.0.4 8 / 19
1.0.3 8 / 19
1.0.2 8 / 19
1.0.1 8 / 19
1.0.0 8 / 19

v1.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mateuspontes → victorhmp (on 2026-04-24, known maintainer) provenance

This version was published by a different npm account (victorhmp) than the most recent previously approved version (mateuspontes) on 2026-04-24, but victorhmp is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: victorhmp → mpcardoso (on 2025-09-01, known maintainer) provenance

This version was published by a different npm account (mpcardoso) than the most recent previously approved version (victorhmp) on 2025-09-01, but mpcardoso is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.