@entur-partner/app-shell-standalone
Exports an AppShellStandalone component to run micro-frontends as a standalone application.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:posthog-js | AI (phantom-deps): posthog-js is a declared runtime dependency; phantom-dep fires because it's used indirectly via config, not a real issue. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 3 / 18 | |
| 7.0.14 | 3 / 18 | |
| 7.0.13 | 3 / 18 | |
| 7.0.12 | 3 / 18 | |
| 7.0.2 | 3 / 0 | |
| 6.1.12 | 3 / 0 | |
| 6.1.10 | 3 / 0 | |
| 6.1.9 | 3 / 0 |
v7.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.