@theia/navigator
Theia - Navigator Extension
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Known maintainer transition on well-vetted monorepo, long track record since. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ndoschek is a verified Theia org maintainer with 546 approved packages; stable for this package. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): Sibling package in the eclipse-theia monorepo; same publisher and release cadence, not an independent risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Eclipse Theia monorepo; provenance attestation not used across the entire package family. | ai | |
| license | weak-copyleft-license:EPL-2.0 | AI (license): EPL-2.0 is the standard Eclipse Theia license; stable across all versions of this package. | ai | |
| license | uncommon-license:Classpath-exception-2.0 | AI (license): Classpath-exception-2.0 is part of the standard Eclipse Theia dual-license; stable across all versions. | ai | |
| license | copyleft-license:GPL-2.0-only | AI (license): GPL-2.0-only WITH Classpath-exception-2.0 is the standard dual-license for Eclipse Theia; stable across all versions. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 1.73.1 | 5 / 1 | |
| 1.73.0 | 5 / 1 | |
| 1.72.3 | 5 / 1 | |
| 1.72.2 | 5 / 1 | |
| 1.72.1 | 5 / 1 | |
| 1.72.0 | 5 / 1 | |
| 1.71.2 | 5 / 1 | |
| 1.71.1 | 5 / 1 | |
| 1.71.0 | 5 / 1 | |
| 1.70.2 | 5 / 1 | |
| 1.70.1 | 5 / 1 | |
| 1.70.0 | 5 / 1 | |
| 1.69.0 | 5 / 1 | |
| 1.68.2 | 5 / 1 | |
| 1.68.1 | 5 / 1 | |
| 1.68.0 | 5 / 1 | |
| 1.67.0 | 5 / 1 | |
| 1.66.2 | 5 / 1 | |
| 1.66.1 | 5 / 1 | |
| 1.66.0 | 5 / 1 | |
| 1.65.2 | 5 / 1 | |
| 1.65.1 | 5 / 1 | |
| 1.65.0 | 5 / 1 | |
| 1.64.4 | 5 / 1 | |
| 1.64.3 | 5 / 1 | |
| 1.64.2 | 5 / 1 | |
| 1.64.1 | 5 / 1 | |
| 1.64.0 | 5 / 1 | |
| 1.63.3 | 5 / 1 | |
| 1.63.2 | 5 / 1 | |
| 1.63.1 | 5 / 1 | |
| 1.63.0 | 5 / 1 | |
| 1.62.2 | 5 / 1 | |
| 1.62.1 | 5 / 1 | |
| 1.62.0 | 5 / 1 | |
| 1.61.1 | 5 / 1 | |
| 1.61.0 | 5 / 1 | |
| 1.60.2 | 5 / 1 | |
| 1.60.1 | 5 / 1 | |
| 1.60.0 | 5 / 1 | |
| 1.59.0 | 5 / 1 | |
| 1.58.5 | 5 / 1 | |
| 1.58.4 | 5 / 1 | |
| 1.58.3 | 5 / 1 | |
| 1.58.2 | 5 / 1 | |
| 1.58.1 | 5 / 1 | |
| 1.58.0 | 5 / 1 | |
| 1.57.1 | 5 / 1 | |
| 1.57.0 | 5 / 1 | |
| 1.56.0 | 5 / 1 | |
| 1.55.1 | 5 / 1 |
v1.73.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.60.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sgraband) than the most recent previously approved version (tsmaeder) on 2025-02-27, but sgraband 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.
v1.58.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tsmaeder) than the most recent previously approved version (jfaltermeier) on 2025-02-17, but tsmaeder 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.
v1.58.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jfaltermeier) than the most recent previously approved version (sgraband) on 2024-12-16, but jfaltermeier 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.
v1.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.