@entur-partner/app-shell
This package contains micro-frontend components for Entur partner
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:@entur-partner/util | AI (dependencies): Internal @entur-partner org dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@entur-partner/micro-frontend | AI (dependencies): Internal @entur-partner org dependency; consistent with this package's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; no provenance is consistent across all versions of this org's packages. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.5.0 | 4 / 12 | |
| 6.4.7 | 4 / 12 | |
| 6.4.6 | 4 / 12 | |
| 6.2.2 | 4 / 2 | |
| 6.2.1 | 4 / 2 | |
| 6.0.4 | 4 / 2 | |
| 6.0.2 | 4 / 2 | |
| 6.0.1 | 4 / 2 |
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.