@opentripplanner/trip-details
A component for displaying details about a trip planning itinerary
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publisher is confirmed by SLSA provenance attestation; consistent with monorepo automation. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is common and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:@styled-icons/fa-solid | AI (dependencies): Popular icon library; no malicious indicators, stable dependency for this UI package. | ai | |
| dependencies | unvetted-dep:@styled-icons/boxicons-regular | AI (dependencies): Popular icon library; no malicious indicators, stable dependency for this UI package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; sparse README and no keywords are normal for internal UI libs in this ecosystem. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 9.1.3 | 5 / 1 | |
| 9.1.2 | 5 / 1 | |
| 9.1.1 | 5 / 1 | |
| 9.1.0 | 5 / 1 | |
| 9.0.7 | 5 / 1 | |
| 9.0.6 | 5 / 1 | |
| 9.0.5 | 5 / 1 | |
| 9.0.4 | 5 / 1 | |
| 9.0.3 | 5 / 1 | |
| 9.0.2 | 3 / 1 | |
| 9.0.1 | 3 / 1 | |
| 9.0.0 | 3 / 1 |
v9.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.1
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 (binh-dam-ibigroup) than the most recent previously approved version (evansiroky) on 2026-01-27, but binh-dam-ibigroup 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.
v9.1.0
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 (binh-dam-ibigroup) than the most recent previously approved version (evansiroky) on 2026-01-05, but binh-dam-ibigroup 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.
v9.0.7
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 (binh-dam-ibigroup) than the most recent previously approved version (evansiroky) on 2026-01-02, but binh-dam-ibigroup 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.
v9.0.6
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 (binh-dam-ibigroup) than the most recent previously approved version (evansiroky) on 2025-12-18, but binh-dam-ibigroup 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.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.