@faststore/components
<p align="center"> <a href="https://faststore.dev"> <img alt="Faststore" src="../ui/static/logo.png" width="60" /> </a> </p> <h1 align="center"> FastStore Components </h1> <p align="center"> <strong> FastStore UI components without style lay
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is a CI config change, not a supply chain risk for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): v4.x restructure ships src/ alongside dist/; large file count reflects package layout change, not injected code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established VTEX monorepo component package; sparse README/keywords are a documentation style choice, not spam. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD is confirmed by SLSA provenance attestation on vtex/faststore repo. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are consistent with a team-managed VTEX org package migrating to CI/CD publishing. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is a known pattern for org-managed packages; SLSA attestation confirms legitimacy. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 2 / 15 | |
| 4.3.0 | 2 / 15 | |
| 4.1.1 | 2 / 15 | |
| 4.1.0 | 2 / 14 | |
| 4.0.0 | 2 / 14 | |
| 3.99.4 | 5 / 14 | |
| 3.99.1 | 5 / 14 | |
| 3.99.0 | 5 / 14 | |
| 3.98.1 | 5 / 14 | |
| 3.98.0 | 5 / 14 | |
| 3.97.0 | 3 / 13 | |
| 3.96.0 | 3 / 13 | |
| 3.95.0 | 3 / 13 | |
| 3.94.0 | 3 / 13 | |
| 3.93.0 | 3 / 13 | |
| 3.92.0 | 3 / 13 | |
| 3.91.2 | 3 / 13 | |
| 3.89.2 | 3 / 13 | |
| 3.88.0 | 3 / 13 | |
| 3.87.0 | 3 / 13 | |
| 3.86.4 | 3 / 13 | |
| 3.84.0 | 3 / 13 | |
| 3.81.0 | 3 / 13 | |
| 3.80.0 | 3 / 13 | |
| 3.78.0 | 3 / 13 | |
| 3.70.2 | 3 / 13 | |
| 3.68.0 | 3 / 13 | |
| 3.65.0 | 3 / 13 | |
| 3.56.1 | 3 / 13 | |
| 3.50.3 | 3 / 13 | |
| 3.49.1 | 3 / 13 | |
| 3.45.0 | 3 / 13 | |
| 3.44.0 | 3 / 13 | |
| 3.42.0 | 3 / 13 | |
| 3.41.3 | 3 / 13 | |
| 3.38.3 | 3 / 13 | |
| 3.28.0 | 3 / 13 | |
| 3.26.0 | 3 / 13 | |
| 3.25.11 | 3 / 13 | |
| 3.22.2 | 3 / 13 | |
| 3.22.0 | 3 / 13 | |
| 3.20.0 | 3 / 13 | |
| 3.18.0 | 3 / 13 | |
| 3.17.0 | 3 / 13 | |
| 3.16.0 | 3 / 13 | |
| 3.15.3 | 3 / 13 | |
| 3.15.0 | 0 / 9 | |
| 3.14.2 | 0 / 9 | |
| 3.13.1 | 0 / 9 | |
| 3.11.4 | 0 / 9 | |
| 3.11.3 | 0 / 9 | |
| 3.11.2 | 0 / 11 | |
| 3.9.2 | 0 / 11 | |
| 3.9.0 | 0 / 13 | |
| 3.7.0 | 0 / 13 | |
| 3.5.0 | 0 / 13 | |
| 3.4.4 | 0 / 13 | |
| 3.4.3 | 0 / 13 | |
| 3.4.2 | 0 / 13 | |
| 3.4.1 | 0 / 13 | |
| 3.1.3 | 0 / 13 | |
| 3.1.0 | 0 / 13 | |
| 3.0.160 | 0 / 13 | |
| 3.0.152 | 0 / 13 | |
| 3.0.150 | 0 / 13 | |
| 3.0.144 | 0 / 13 | |
| 3.0.141 | 0 / 13 | |
| 3.0.135 | 0 / 13 | |
| 3.0.134 | 0 / 13 | |
| 3.0.131 | 0 / 13 | |
| 3.0.116 | 0 / 13 | |
| 3.0.115 | 0 / 13 | |
| 3.0.110 | 0 / 13 | |
| 3.0.109 | 0 / 13 | |
| 3.0.103 | 0 / 13 | |
| 3.0.97 | 0 / 10 | |
| 3.0.96 | 0 / 10 | |
| 3.0.95 | 0 / 10 | |
| 3.0.94 | 0 / 10 | |
| 3.0.89 | 0 / 10 | |
| 3.0.88 | 0 / 10 | |
| 3.0.85 | 0 / 10 | |
| 3.0.81 | 0 / 10 | |
| 3.0.77 | 0 / 10 | |
| 3.0.75 | 0 / 10 | |
| 3.0.74 | 0 / 10 | |
| 3.0.68 | 0 / 10 | |
| 3.0.66 | 0 / 10 | |
| 3.0.63 | 0 / 10 | |
| 3.0.54 | 0 / 10 | |
| 3.0.47 | 0 / 10 | |
| 3.0.46 | 0 / 10 | |
| 3.0.44 | 0 / 10 |
v4.4.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v3.41.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.