@codingame/monaco-vscode-chat-service-override
VSCode public API plugged on the monaco editor - chat service-override
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): New source files correspond to new internal sub-package dependencies in a major version bump of this monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version release after gap is consistent with VSCode upstream release cycle for this monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are same-org @codingame/monaco-vscode-*-common packages pinned to the same version; monorepo refactoring pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-64322fa2-7385-5f46-935b-8f243d98004b-common | AI (dependencies): Internal CodinGame split package, same org and version as parent; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-88141f48-1af9-57ef-a278-f4b2ff6128fa-common | AI (dependencies): Internal CodinGame split package, same org and version as parent; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-af7aa6ff-f023-5da1-803d-a085ef0e5dc3-common | AI (dependencies): Internal CodinGame split package, same org and version as parent; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-f1bbc6d3-6129-583c-a2ba-c80b832993d2-common | AI (dependencies): Internal CodinGame split package, same org and version as parent; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-8c844347-a703-5de1-9eeb-5e0c7f503a58-common | AI (dependencies): Internal CodinGame split package, same org and version as parent; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-07eaa805-9dea-5ec6-a422-a4f04872424d-common | AI (dependencies): Internal CodinGame split package, same org and version as parent; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-1021b67c-93e5-5c78-a270-cbdb2574d980-common | AI (dependencies): Internal CodinGame split package, same org and version as parent; stable pattern across all releases. | ai | |
| provenance | no-provenance | AI (provenance): Established CodinGame org package; no provenance is consistent across all 236 versions of this family. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 32.0.2 | 4 / 0 | |
| 32.0.1 | 4 / 0 | |
| 32.0.0 | 4 / 0 | |
| 31.0.1 | 4 / 0 | |
| 31.0.0 | 4 / 0 | |
| 30.0.1 | 4 / 0 | |
| 30.0.0 | 4 / 0 | |
| 29.1.1 | 4 / 0 | |
| 29.1.0 | 4 / 0 | |
| 29.0.0 | 4 / 0 | |
| 28.4.1 | 4 / 0 | |
| 28.4.0 | 4 / 0 | |
| 28.3.1 | 4 / 0 | |
| 28.3.0 | 4 / 0 | |
| 28.2.0 | 4 / 0 | |
| 28.1.2 | 4 / 0 | |
| 28.1.1 | 4 / 0 | |
| 28.0.1 | 4 / 0 | |
| 28.0.0 | 4 / 0 | |
| 27.0.0 | 4 / 0 | |
| 26.2.2 | 4 / 0 | |
| 26.2.1 | 4 / 0 | |
| 26.2.0 | 4 / 0 | |
| 26.1.2 | 4 / 0 | |
| 26.1.1 | 4 / 0 | |
| 26.1.0 | 4 / 0 | |
| 26.0.1 | 4 / 0 | |
| 26.0.0 | 4 / 0 | |
| 25.1.2 | 4 / 0 | |
| 25.1.1 | 4 / 0 | |
| 25.1.0 | 4 / 0 | |
| 25.0.1 | 4 / 0 | |
| 25.0.0 | 4 / 0 | |
| 24.3.0 | 4 / 0 | |
| 24.2.0 | 4 / 0 | |
| 24.1.1 | 4 / 0 | |
| 24.1.0 | 4 / 0 | |
| 23.3.0 | 40 / 0 | |
| 23.2.2 | 40 / 0 | |
| 23.2.1 | 40 / 0 | |
| 23.2.0 | 40 / 0 | |
| 23.1.1 | 40 / 0 | |
| 23.1.0 | 42 / 0 | |
| 23.0.4 | 42 / 0 | |
| 23.0.3 | 42 / 0 | |
| 23.0.2 | 42 / 0 | |
| 23.0.1 | 42 / 0 | |
| 23.0.0 | 42 / 0 | |
| 22.1.9 | 39 / 0 | |
| 22.1.5 | 40 / 0 | |
| 22.1.4 | 40 / 0 |
v32.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.