@replit/codemirror-lang-csharp
A C# mode for CodeMirror 6
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer, no behavioral change; matches publisher-changed-known-maintainer context. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Replit team roster change, consistent with known org maintainers. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Departing maintainer replaced by other Replit staff, no takeover indicators. | ai |
v6.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: giuseppeatreplit.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (giuseppeatreplit) than the most recent previously approved version (alan_at_replit) on 2023-02-22, but giuseppeatreplit 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.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.