@codingame/monaco-vscode-1ba786a5-b7d7-5d26-8a85-ae48ee2a74a4-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-9c1add21-d437-5ee3-ae2b-ad115a9ef171-common | AI (dependencies): Sibling auto-generated package within same trusted monorepo family. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Routine internal dep-hash rotation typical of this generated package family. | ai |
Versions (showing 9 of 9)
| 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 | |
| 19.0.0 | 2 / 0 | |
| 17.2.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.
v19.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.