@vtex/faststore-plugin-buyer-portal
A plugin for faststore with buyer portal
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT payload decoding pattern; not obfuscation or exfiltration. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer dep and framework-level dep; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only dev dep loaded by convention; stable false positive for this package. | ai |
Versions (showing 21 of 223)
| Version | Deps | Published |
|---|---|---|
| 1.1.8 | 2 / 6 | |
| 1.1.7 | 2 / 6 | |
| 1.1.6 | 2 / 6 | |
| 1.1.5 | 2 / 6 | |
| 1.1.4 | 2 / 6 | |
| 1.1.3 | 2 / 6 | |
| 1.1.2 | 2 / 6 | |
| 1.1.1 | 3 / 5 | |
| 1.0.50 | 3 / 5 | |
| 1.0.49 | 2 / 5 | |
| 1.0.48 | 2 / 5 | |
| 1.0.47 | 2 / 5 | |
| 1.0.46 | 2 / 5 | |
| 1.0.45 | 2 / 5 | |
| 1.0.44 | 2 / 5 | |
| 1.0.43 | 2 / 5 | |
| 1.0.42 | 2 / 5 | |
| 1.0.41 | 2 / 5 | |
| 1.0.40 | 2 / 5 | |
| 1.0.39 | 2 / 5 | |
| 1.0.38 | 2 / 5 |
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.