← Home

@replit/codemirror-indentation-markers

npm Repository Homepage

Render indentation markers in CodeMirror

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

sareinikrishatreplitmikewesthadmotzyballreplitdstewartryanweingasttheflowingskyjonesit-replitszymon_kcdmistmanjackyzha0jamesaustinreplitlopezhoraciobradymaddenreplitryantmalexisreplitink404brianpooltobyhobrenoafbmasad-frostlincolnreplitstkennedreplitmattcbrewsterltazmin_replitmoudylhchavez

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from schestakov to bradymaddenreplit reflects normal Replit team turnover; both are clearly Replit employees. ai
maintainer-change maintainer-added AI (maintainer-change): All new maintainers have 'replit' in their names, consistent with organizational team changes at Replit. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers are former Replit team members; normal org turnover for a scoped @replit package. ai

Versions (showing 17 of 17)

Version Deps Published
6.5.3 0 / 9
6.5.2 0 / 9
6.5.1 0 / 9
6.5.0 0 / 9
6.4.3 0 / 9
6.4.2 0 / 9
6.4.1 0 / 9
6.4.0 0 / 9
6.3.0 0 / 9
6.2.2 0 / 9
6.2.1 0 / 9
6.2.0 0 / 9
6.1.0 0 / 8
6.0.0 0 / 8
0.20.0 0 / 8
0.19.1 0 / 9
0.19.0 0 / 9

v6.5.1

2 findings
HIGH Publisher changed: schestakov → bradymaddenreplit (on 2024-03-13) provenance

This version was published by a different npm account than previous versions on 2024-03-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.