@faststore/api MIT 44 versions

@faststore/api

npm Repository Homepage

<p align="center"> <a href="https://faststore.dev"> <img alt="Faststore" src="../ui/static/logo.png" width="60" /> </a> </p> <h1 align="center"> FastStore API </h1> <p align="center"> <strong> Connect to your favorite ecommerce platform

44

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

emersonlaurentinoguieevcmarcos_vtexlariciamotaeduardo.formigahellofanny

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@graphql-tools/load-files	AI (phantom-deps): Used in codegen config, not a direct import; stable pattern.	ai	2026/07/09
provenance	missing-githead	AI (provenance): CI metadata gap, provenance direction unchanged and SLSA attestation present.	ai	2026/07/09
provenance	publisher-changed	AI (provenance): Manual-to-CI/CD attested publish switch; improvement, not compromise.	ai	2026/07/09
maintainer-change	maintainer-added	AI (maintainer-change): Legitimate team maintainers added alongside CI provenance switch.	ai	2026/07/09
semgrep	semgrep:base64-decode	AI (semgrep): Standard JWT payload parsing (split on '.', decode base64 middle segment); not obfuscation.	ai	2026/05/17
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped VTEX faststore package; no relation to hapi. Levenshtein match is coincidental.	ai	2026/05/17
phantom-deps	phantom-dep:@rollup/plugin-graphql	AI (phantom-deps): Build-time rollup plugin used by convention in build config, not directly imported in source.	ai	2026/05/17
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped VTEX faststore package; no relation to pg. Levenshtein match is coincidental.	ai	2026/05/17
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped VTEX faststore package; no relation to joi. Levenshtein match is coincidental.	ai	2026/05/17
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped VTEX faststore package; no relation to ajv. Levenshtein match is coincidental.	ai	2026/05/17

Versions (showing 44 of 144)

Version	Deps	Published
3.4.4	14 / 21	2024-12-20
3.4.3	14 / 21	2024-12-20
3.4.2	14 / 21	2024-12-20
3.4.1	14 / 21	2024-12-20
3.1.3	14 / 21	2024-12-13
3.0.160	14 / 21	2024-12-09
3.0.157	14 / 21	2024-12-04
3.0.152	14 / 21	2024-11-21
3.0.150	14 / 21	2024-11-19
3.0.149	14 / 21	2024-11-13
3.0.140	14 / 21	2024-10-31
3.0.135	14 / 21	2024-10-18
3.0.134	14 / 21	2024-10-17
3.0.131	14 / 21	2024-10-11
3.0.130	14 / 21	2024-10-10
3.0.129	14 / 21	2024-10-09
3.0.124	14 / 21	2024-10-04
3.0.122	14 / 21	2024-10-03
3.0.120	14 / 21	2024-10-03
3.0.117	14 / 21	2024-10-01
3.0.116	14 / 21	2024-09-27
3.0.110	14 / 21	2024-09-24
3.0.109	14 / 21	2024-09-23
3.0.108	14 / 21	2024-09-16
3.0.107	14 / 21	2024-09-16
3.0.100	14 / 21	2024-09-10
3.0.99	14 / 21	2024-09-05
3.0.98	14 / 21	2024-09-04
3.0.97	14 / 21	2024-09-03
3.0.95	14 / 21	2024-08-23
3.0.94	14 / 21	2024-08-22
3.0.88	14 / 21	2024-07-19
3.0.76	14 / 21	2024-07-02
3.0.75	14 / 21	2024-06-26
3.0.74	14 / 21	2024-06-26
3.0.68	14 / 21	2024-06-06
3.0.66	14 / 21	2024-06-04
3.0.65	14 / 21	2024-06-04
3.0.63	14 / 21	2024-05-29
3.0.54	14 / 20	2024-05-13
3.0.51	14 / 20	2024-05-09
3.0.47	14 / 20	2024-05-06
3.0.46	14 / 20	2024-05-06
3.0.44	14 / 20	2024-05-03

v3.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.160

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.157

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.152

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.150

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.149

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.140

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.135

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.134

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.131

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.130

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.129

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.124

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.122

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.120

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.117

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.116

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.110

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.109

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.108

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.107

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.100

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.99

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.98

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.97

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.95

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.94

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.88

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.76

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.75

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.74

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.68

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.66

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.65

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.63

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.54

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.51

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.47

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.46

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.44

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.