← Home

@diplodoc/yfmlint

npm Repository Homepage

YFM (Yandex Flavored Markdown) syntax linter with custom rules for Diplodoc platform

29
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rndnmrobot-dataui-npmalexey_w1003y3martyanov-avvseshmakhnatkindiplodoc-botreazy015goldsergseparatrix

Keywords

docsyfmyfmlintmarkdownlintdocumentation

Versions (showing 29 of 29)

Version Deps Published
1.9.0 0 / 15
1.8.0 0 / 15
1.7.7 0 / 15
1.7.6 0 / 16
1.7.5 0 / 15
1.7.4 0 / 15
1.7.3 0 / 15
1.7.2 0 / 15
1.7.1 0 / 15
1.7.0 0 / 15
1.6.0 0 / 15
1.4.0 0 / 15
1.3.5 0 / 15
1.3.4 0 / 16
1.3.3 0 / 14
1.3.2 0 / 14
1.3.1 0 / 14
1.3.0 0 / 14
1.2.8 0 / 14
1.2.7 0 / 14
1.2.6 0 / 14
1.2.5 0 / 14
1.2.4 0 / 14
1.2.3 0 / 14
1.2.2 0 / 14
1.2.1 0 / 14
1.2.0 0 / 14
1.1.0 0 / 14
1.0.0 0 / 14

v1.9.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.8.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: 3y3 → robot-dataui-npm (on 2025-03-13, known maintainer) provenance

This version was published by a different npm account (robot-dataui-npm) than the most recent previously approved version (3y3) on 2025-03-13, but robot-dataui-npm 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.

v1.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: 3y3 → robot-dataui-npm (on 2025-03-11, known maintainer) provenance

This version was published by a different npm account (robot-dataui-npm) than the most recent previously approved version (3y3) on 2025-03-11, but robot-dataui-npm 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.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.