@entur/menu
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:@entur/layout | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is unreliable for monorepo packages that may re-export without direct import. | ai | |
| dependencies | unvetted-dep:@entur/icons | AI (dependencies): Sibling package in the same @entur design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@entur/utils | AI (dependencies): Sibling package in the same @entur design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@entur/button | AI (dependencies): Sibling package in the same @entur design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@entur/a11y | AI (dependencies): Sibling package in the same @entur design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@entur/tooltip | AI (dependencies): Sibling package in the same @entur design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@entur/typography | AI (dependencies): Sibling package in the same @entur design system monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@entur/expand | AI (dependencies): Sibling package in the same @entur design system monorepo; stable pattern across all versions. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 10 / 10 | |
| 6.1.6 | 10 / 10 | |
| 6.1.5 | 10 / 10 | |
| 6.1.4 | 10 / 10 | |
| 6.1.3 | 10 / 11 | |
| 6.1.2 | 10 / 11 | |
| 6.1.1 | 10 / 11 | |
| 6.1.0 | 10 / 11 | |
| 6.0.2 | 11 / 11 | |
| 6.0.1 | 11 / 11 | |
| 6.0.0 | 11 / 11 | |
| 5.3.1 | 11 / 11 | |
| 5.3.0 | 11 / 11 | |
| 5.2.7 | 11 / 11 |
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.