@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 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 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 |
v4.1.1
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.
v4.1.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.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.99.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.99.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.99.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.98.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.98.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.91.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.89.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.86.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.50.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.