@theia/mini-browser
Theia - Mini-Browser 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): Eclipse Theia monorepo uses GitHub Actions for automated publishing; SLSA attestation confirms CI/CD provenance. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ndoschek is a trusted eclipse-theia org maintainer with 1086 approved packages; rotation is expected in large monorepos. | ai | |
| dependencies | unvetted-dep:@theia/core | AI (dependencies): Sibling Theia monorepo package; versioned in lockstep, stable pattern across all Theia releases. | ai | |
| dependencies | unvetted-dep:@theia/filesystem | AI (dependencies): Sibling Theia monorepo package; versioned in lockstep, stable pattern across all Theia releases. | ai | |
| phantom-deps | phantom-dep:@types/mime-types | AI (phantom-deps): @types/mime-types is a TypeScript type declaration used at compile time; stable false positive for this package. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 1.73.1 | 7 / 1 | |
| 1.73.0 | 7 / 1 | |
| 1.72.3 | 7 / 1 | |
| 1.72.2 | 7 / 1 | |
| 1.72.1 | 7 / 1 | |
| 1.72.0 | 7 / 1 | |
| 1.71.2 | 7 / 1 | |
| 1.71.1 | 7 / 1 | |
| 1.71.0 | 7 / 1 | |
| 1.70.2 | 7 / 1 | |
| 1.70.1 | 7 / 1 | |
| 1.70.0 | 7 / 1 | |
| 1.69.0 | 7 / 1 | |
| 1.68.2 | 7 / 1 | |
| 1.68.1 | 7 / 1 | |
| 1.68.0 | 7 / 1 | |
| 1.67.0 | 7 / 1 | |
| 1.66.2 | 7 / 1 | |
| 1.66.1 | 7 / 1 | |
| 1.66.0 | 7 / 1 | |
| 1.65.2 | 7 / 1 | |
| 1.65.1 | 7 / 1 | |
| 1.65.0 | 7 / 1 | |
| 1.64.4 | 7 / 1 | |
| 1.64.3 | 7 / 1 | |
| 1.64.2 | 7 / 1 | |
| 1.64.1 | 7 / 1 | |
| 1.64.0 | 7 / 1 | |
| 1.63.3 | 7 / 1 | |
| 1.63.2 | 7 / 1 | |
| 1.63.1 | 7 / 1 | |
| 1.63.0 | 7 / 1 | |
| 1.62.2 | 7 / 1 | |
| 1.62.1 | 7 / 1 | |
| 1.62.0 | 7 / 1 | |
| 1.61.1 | 7 / 1 | |
| 1.61.0 | 7 / 1 | |
| 1.60.2 | 7 / 1 | |
| 1.60.1 | 7 / 1 | |
| 1.60.0 | 7 / 1 | |
| 1.59.0 | 7 / 1 | |
| 1.58.5 | 7 / 1 | |
| 1.58.4 | 7 / 1 | |
| 1.58.3 | 7 / 1 | |
| 1.58.2 | 7 / 1 | |
| 1.58.1 | 7 / 1 | |
| 1.58.0 | 7 / 1 | |
| 1.57.1 | 7 / 1 | |
| 1.57.0 | 7 / 1 | |
| 1.56.0 | 7 / 1 | |
| 1.55.1 | 7 / 1 | |
| 1.55.0 | 7 / 1 | |
| 1.54.0 | 7 / 1 | |
| 1.53.2 | 7 / 1 | |
| 1.53.1 | 7 / 1 | |
| 1.53.0 | 7 / 1 | |
| 1.52.0 | 7 / 1 | |
| 1.51.0 | 7 / 1 | |
| 1.50.1 | 7 / 1 | |
| 1.50.0 | 7 / 1 | |
| 1.49.1 | 7 / 1 | |
| 1.49.0 | 7 / 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.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-10-31, 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.54.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 2024-09-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.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.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 (jfaltermeier) than the most recent previously approved version (sgraband) on 2024-09-04, 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.53.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-08-29, 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.52.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-07-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.