@codingame/monaco-vscode-86d65fc6-30f9-5dca-9501-e249de688591-common
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@codingame/monaco-vscode-ca445022-b812-53ca-a041-e46c7e0b13de-common | AI (dependencies): Sibling auto-generated codingame package, same version pin, expected churn. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Generated split packages routinely swap sibling deps between releases. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-managed automated publishing; maintainer list churn expected, no takeover indicators. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 19.1.4 | 2 / 0 | |
| 19.1.3 | 2 / 0 | |
| 19.1.2 | 2 / 0 | |
| 19.1.1 | 2 / 0 | |
| 19.1.0 | 2 / 0 | |
| 19.0.2 | 2 / 0 | |
| 19.0.1 | 2 / 0 | |
| 16.1.1 | 2 / 0 |
v19.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.