@faststore/api
<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
Supply chain provenance
Status for the latest visible version.
Maintainers
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 | |
| provenance | missing-githead | AI (provenance): CI metadata gap, provenance direction unchanged and SLSA attestation present. | ai | |
| provenance | publisher-changed | AI (provenance): Manual-to-CI/CD attested publish switch; improvement, not compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate team maintainers added alongside CI provenance switch. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT payload parsing (split on '.', decode base64 middle segment); not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped VTEX faststore package; no relation to hapi. Levenshtein match is coincidental. | ai | |
| 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 | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped VTEX faststore package; no relation to pg. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped VTEX faststore package; no relation to joi. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped VTEX faststore package; no relation to ajv. Levenshtein match is coincidental. | ai |
Versions (showing 51 of 144)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 10 / 20 | |
| 4.3.0 | 10 / 20 | |
| 4.1.1 | 10 / 20 | |
| 4.1.0 | 10 / 19 | |
| 4.0.0 | 10 / 19 | |
| 3.99.4 | 10 / 17 | |
| 3.99.1 | 10 / 17 | |
| 3.99.0 | 10 / 17 | |
| 3.98.0 | 10 / 17 | |
| 3.97.1 | 10 / 17 | |
| 3.97.0 | 10 / 17 | |
| 3.96.3 | 10 / 17 | |
| 3.96.2 | 10 / 17 | |
| 3.96.1 | 10 / 17 | |
| 3.96.0 | 10 / 17 | |
| 3.95.0 | 10 / 17 | |
| 3.94.0 | 10 / 17 | |
| 3.93.0 | 10 / 17 | |
| 3.92.0 | 10 / 17 | |
| 3.91.2 | 10 / 17 | |
| 3.91.0 | 10 / 17 | |
| 3.90.0 | 10 / 17 | |
| 3.89.4 | 10 / 17 | |
| 3.89.3 | 10 / 17 | |
| 3.89.2 | 10 / 17 | |
| 3.89.1 | 10 / 17 | |
| 3.88.6 | 10 / 17 | |
| 3.88.2 | 10 / 17 | |
| 3.88.1 | 10 / 17 | |
| 3.87.0 | 10 / 17 | |
| 3.85.0 | 10 / 17 | |
| 3.84.5 | 10 / 17 | |
| 3.84.4 | 10 / 17 | |
| 3.84.1 | 10 / 17 | |
| 3.84.0 | 10 / 17 | |
| 3.82.4 | 10 / 17 | |
| 3.82.0 | 10 / 17 | |
| 3.81.0 | 10 / 17 | |
| 3.80.0 | 10 / 17 | |
| 3.79.0 | 10 / 17 | |
| 3.78.0 | 10 / 17 | |
| 3.73.0 | 10 / 17 | |
| 3.72.0 | 10 / 17 | |
| 3.71.0 | 10 / 17 | |
| 3.69.0 | 10 / 17 | |
| 3.68.1 | 10 / 17 | |
| 3.68.0 | 10 / 17 | |
| 3.66.0 | 10 / 17 | |
| 3.65.1 | 10 / 17 | |
| 3.65.0 | 10 / 17 | |
| 3.64.0 | 10 / 17 |
v4.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.97.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.97.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.96.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.96.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.96.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.96.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.