@moonbase.sh/storefront
Package to let you embed Moonbase.sh into your storefront as a payment and delivery provider
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@heroicons/vue | AI (dependencies): @heroicons/vue is a widely-used, well-maintained UI icon library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pinia | AI (phantom-deps): Vue component library; pinia referenced in config/setup files, not direct imports — stable false positive. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Utility referenced in config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:chroma-js | AI (phantom-deps): Color utility referenced in config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@heroicons/vue | AI (phantom-deps): Icon library referenced in config; stable false positive for this Vue component package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 6 / 11 | |
| 2.4.3 | 6 / 11 | |
| 2.4.2 | 6 / 11 | |
| 2.4.1 | 6 / 11 | |
| 2.4.0 | 6 / 11 | |
| 2.3.0 | 6 / 11 | |
| 2.2.1 | 6 / 11 | |
| 2.2.0 | 6 / 11 | |
| 2.0.2 | 6 / 11 | |
| 2.0.1 | 6 / 11 | |
| 2.0.0 | 6 / 11 | |
| 1.0.37 | 6 / 11 | |
| 1.0.36 | 6 / 11 | |
| 1.0.35 | 6 / 11 | |
| 1.0.34 | 6 / 11 | |
| 1.0.33 | 6 / 11 | |
| 1.0.32 | 6 / 11 | |
| 1.0.31 | 6 / 11 | |
| 1.0.30 | 6 / 11 | |
| 1.0.29 | 6 / 11 | |
| 1.0.28 | 6 / 11 | |
| 1.0.27 | 6 / 11 | |
| 1.0.26 | 6 / 11 | |
| 1.0.25 | 6 / 11 | |
| 1.0.24 | 6 / 11 | |
| 1.0.23 | 6 / 11 | |
| 1.0.22 | 6 / 10 | |
| 1.0.21 | 6 / 10 | |
| 1.0.16 | 6 / 10 | |
| 1.0.15 | 6 / 10 | |
| 0.4.51 | 6 / 10 |
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.