@entur-partner/micro-frontend
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher has strong 288/0 track record; no code changes accompany the switch. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with legitimate maintainer handoff, no behavioral change. | ai | |
| provenance | no-provenance | AI (provenance): Internal org package published via GitHub Actions; provenance not configured but no malicious indicators. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.10.0 | 1 / 3 | |
| 2.9.0 | 1 / 3 | |
| 2.8.0 | 1 / 3 | |
| 2.7.7 | 1 / 3 | |
| 2.7.6 | 1 / 3 | |
| 2.7.4 | 1 / 3 | |
| 2.7.3 | 1 / 3 | |
| 2.7.2 | 1 / 3 | |
| 2.7.1 | 1 / 3 | |
| 2.7.0 | 1 / 3 | |
| 2.6.5 | 1 / 3 | |
| 2.6.4 | 1 / 3 | |
| 2.6.3 | 1 / 3 | |
| 2.6.2 | 1 / 3 | |
| 2.6.1 | 1 / 3 | |
| 2.6.0 | 1 / 3 | |
| 2.5.0 | 1 / 3 | |
| 2.4.8 | 1 / 2 | |
| 2.4.7 | 1 / 2 | |
| 2.4.5 | 1 / 2 |
v2.4.8
2 findingsThis version was published by a different npm account than previous versions on 2025-03-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
2 findingsThis version was published by a different npm account than previous versions on 2025-02-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.