@entur/tooltip
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation in a large, established org package; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@entur/icons | AI (dependencies): Sibling package in the Entur design-system monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@entur/utils | AI (dependencies): Sibling package in the Entur design-system monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@entur/button | AI (dependencies): Sibling package in the Entur design-system monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@entur/layout | AI (dependencies): Sibling package in the Entur design-system monorepo; expected dependency. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 5.3.12 | 8 / 10 | |
| 5.3.11 | 8 / 10 | |
| 5.3.10 | 8 / 10 | |
| 5.3.9 | 8 / 10 | |
| 5.3.8 | 8 / 11 | |
| 5.3.7 | 8 / 11 | |
| 5.3.6 | 8 / 11 | |
| 5.3.5 | 8 / 11 | |
| 5.3.4 | 8 / 11 | |
| 5.3.3 | 8 / 11 | |
| 5.3.2 | 8 / 11 | |
| 5.3.1 | 8 / 11 | |
| 5.3.0 | 8 / 11 | |
| 5.2.18 | 8 / 11 | |
| 5.2.17 | 8 / 11 | |
| 5.2.16 | 8 / 11 | |
| 5.2.15 | 8 / 11 | |
| 5.2.14 | 8 / 11 | |
| 5.2.13 | 8 / 11 | |
| 5.2.12 | 8 / 1 | |
| 5.2.11 | 8 / 1 | |
| 5.2.10 | 8 / 1 | |
| 5.2.9 | 8 / 1 |
v5.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ceciliehrr) than the most recent previously approved version (magnusrand) on 2025-10-20, but ceciliehrr is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ceciliehrr) than the most recent previously approved version (magnusrand) on 2025-10-17, but ceciliehrr is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (magnusrand) than the most recent previously approved version (ceciliehrr) on 2025-08-29, but magnusrand is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.