@theia/search-in-workspace
Theia - Search in workspace
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): ndoschek is an established Eclipse Theia org publisher with 546 approved packages; routine team rotation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes ripgrep binary search results (bytes field) to string — documented ripgrep JSON output format, not malicious. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 1.73.1 | 10 / 1 | |
| 1.73.0 | 10 / 1 | |
| 1.72.3 | 10 / 1 | |
| 1.72.2 | 10 / 1 | |
| 1.72.1 | 10 / 1 | |
| 1.72.0 | 10 / 1 | |
| 1.71.2 | 10 / 1 | |
| 1.71.1 | 10 / 1 | |
| 1.71.0 | 10 / 1 | |
| 1.70.2 | 10 / 1 | |
| 1.70.1 | 10 / 1 | |
| 1.70.0 | 10 / 1 | |
| 1.69.0 | 10 / 1 | |
| 1.68.2 | 10 / 1 | |
| 1.68.1 | 10 / 1 | |
| 1.68.0 | 10 / 1 | |
| 1.67.0 | 10 / 1 | |
| 1.66.2 | 10 / 1 | |
| 1.66.1 | 10 / 1 | |
| 1.66.0 | 10 / 1 | |
| 1.65.2 | 10 / 1 | |
| 1.65.1 | 10 / 1 | |
| 1.65.0 | 10 / 1 | |
| 1.64.4 | 10 / 1 | |
| 1.64.3 | 10 / 1 | |
| 1.64.2 | 10 / 1 | |
| 1.64.1 | 10 / 1 | |
| 1.64.0 | 10 / 1 | |
| 1.63.3 | 10 / 1 | |
| 1.63.2 | 10 / 1 | |
| 1.63.1 | 10 / 1 | |
| 1.63.0 | 10 / 1 | |
| 1.62.2 | 10 / 1 | |
| 1.62.1 | 10 / 1 | |
| 1.62.0 | 10 / 1 | |
| 1.61.1 | 10 / 1 | |
| 1.61.0 | 10 / 1 | |
| 1.60.2 | 10 / 1 | |
| 1.60.1 | 10 / 1 | |
| 1.60.0 | 10 / 1 | |
| 1.59.0 | 10 / 1 | |
| 1.58.5 | 10 / 1 | |
| 1.58.4 | 10 / 1 | |
| 1.58.3 | 10 / 1 | |
| 1.58.2 | 10 / 1 | |
| 1.58.1 | 10 / 1 | |
| 1.58.0 | 10 / 1 | |
| 1.57.1 | 10 / 1 | |
| 1.57.0 | 10 / 1 | |
| 1.56.0 | 10 / 1 | |
| 1.55.1 | 10 / 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.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 (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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.3
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 (tsmaeder) than the most recent previously approved version (jfaltermeier) on 2025-02-18, 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.2
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 (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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.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 (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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2024-12-03, 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.