@opensumi/ide-components
@opensumi/ide-components
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo scoped package; missing repo/keywords in published manifest is a known pattern for opensumi packages. | ai | |
| dependencies | unvetted-dep:@opensumi/ide-core-common | AI (dependencies): Sibling monorepo package released at same version; not an independent unvetted dependency. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 22 / 3 | |
| 3.8.2 | 21 / 4 | |
| 3.8.1 | 21 / 4 | |
| 3.8.0 | 21 / 4 | |
| 3.7.1 | 21 / 4 | |
| 3.7.0 | 21 / 4 | |
| 3.6.4 | 21 / 4 | |
| 3.6.3 | 21 / 4 | |
| 3.6.2 | 21 / 4 | |
| 3.6.1 | 21 / 4 | |
| 3.6.0 | 21 / 4 | |
| 3.5.0 | 21 / 4 | |
| 3.4.5 | 21 / 4 | |
| 3.4.4 | 21 / 4 | |
| 3.4.3 | 21 / 4 | |
| 3.4.2 | 21 / 4 | |
| 3.4.1 | 21 / 4 | |
| 3.4.0 | 21 / 4 | |
| 3.3.3 | 21 / 4 | |
| 3.3.2 | 21 / 4 | |
| 3.3.1 | 21 / 4 | |
| 3.3.0 | 21 / 4 | |
| 3.2.5 | 19 / 4 | |
| 3.2.4 | 19 / 4 | |
| 3.2.3 | 19 / 4 | |
| 3.2.2 | 19 / 4 | |
| 3.2.1 | 19 / 4 | |
| 3.2.0 | 19 / 4 | |
| 3.1.4 | 19 / 4 | |
| 3.1.3 | 19 / 4 | |
| 3.1.2 | 19 / 4 | |
| 3.1.1 | 19 / 4 | |
| 3.1.0 | 19 / 4 | |
| 3.0.4 | 19 / 4 |
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.