@theia/debug
Theia - Debug 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): ndoschek is an established Theia project maintainer with 837 approved packages; publisher rotation within the org is expected. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same rationale: ndoschek is a known trusted Theia contributor, not an external takeover. | ai | |
| dependencies | unvetted-dep:@theia/test | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/editor | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/monaco | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/output | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/console | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/markers | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/process | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/workspace | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/filesystem | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/variable-resolver | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/monaco-editor-core | AI (dependencies): Theia-maintained Monaco fork; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:@theia/markers | AI (phantom-deps): Same-org sibling; phantom-dep heuristic unreliable for monorepo indirect usage. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Used via config/transitive patterns; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@theia/terminal | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai | |
| dependencies | unvetted-dep:@theia/task | AI (dependencies): Sibling monorepo package; always co-released at the same version. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.72.2 | 19 / 1 | |
| 1.72.1 | 19 / 1 | |
| 1.72.0 | 19 / 1 | |
| 1.71.2 | 19 / 1 | |
| 1.71.1 | 19 / 1 | |
| 1.71.0 | 19 / 1 | |
| 1.70.2 | 19 / 1 | |
| 1.70.1 | 19 / 1 | |
| 1.70.0 | 19 / 1 | |
| 1.69.0 | 19 / 1 | |
| 1.68.2 | 19 / 1 | |
| 1.68.1 | 19 / 1 | |
| 1.68.0 | 19 / 1 | |
| 1.67.0 | 19 / 1 | |
| 1.66.2 | 19 / 1 | |
| 1.66.1 | 19 / 1 | |
| 1.66.0 | 19 / 1 | |
| 1.65.2 | 19 / 1 | |
| 1.65.1 | 19 / 1 | |
| 1.65.0 | 19 / 1 | |
| 1.64.4 | 19 / 1 | |
| 1.64.3 | 19 / 1 | |
| 1.64.2 | 19 / 1 | |
| 1.64.1 | 19 / 1 | |
| 1.64.0 | 19 / 1 | |
| 1.63.3 | 19 / 1 | |
| 1.63.2 | 19 / 1 | |
| 1.63.1 | 19 / 1 | |
| 1.63.0 | 19 / 1 | |
| 1.62.2 | 19 / 1 | |
| 1.62.1 | 19 / 1 | |
| 1.62.0 | 19 / 1 | |
| 1.61.1 | 19 / 1 | |
| 1.61.0 | 19 / 1 |
v1.72.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.72.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.72.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.71.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.71.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.71.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.70.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.70.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.69.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. 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.
v1.68.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. 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.
v1.68.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. 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.
v1.68.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-29. 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.
v1.67.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-10. 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.
v1.66.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
This version was published by a different npm account (eclipse-theia-bot) than the most recent previously approved version (sgraband) on 2025-11-10, but eclipse-theia-bot 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.66.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
This version was published by a different npm account (eclipse-theia-bot) than the most recent previously approved version (sgraband) on 2025-11-07, but eclipse-theia-bot 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.66.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
This version was published by a different npm account (eclipse-theia-bot) than the most recent previously approved version (sgraband) on 2025-10-30, but eclipse-theia-bot 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.65.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
This version was published by a different npm account (eclipse-theia-bot) than the most recent previously approved version (sgraband) on 2025-10-14, but eclipse-theia-bot 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.65.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.4
2 findingsThis version was published by a different npm account than previous versions on 2025-10-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.3
2 findingsThis version was published by a different npm account than previous versions on 2025-10-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.2
2 findingsThis version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2025-07-16, 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.63.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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2025-07-07, 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.63.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 2025-07-01, 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.63.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 (jfaltermeier) on 2025-06-26, 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.62.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 (sgraband) than the most recent previously approved version (jfaltermeier) on 2025-06-12, 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.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.