← Home

eslint-plugin-yaml

npm Repository Homepage
7
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

aminya

Keywords

eslinteslintplugineslint-pluginyamlymleslint-plugin-yamleslint-plugin-yml

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/YamlProcessor.js AI (source-diff): Readable compiled TS output from new vite build, not true obfuscation. ai
phantom-deps phantom-dep:eslint-plugin-yaml AI (phantom-deps): Self-link (link:) used for local test tooling, not a real dependency. ai
phantom-deps phantom-dep:@types/estree AI (phantom-deps): Type-only convention dependency, expected to be unimported. ai

Versions (showing 7 of 7)

Version Deps Published
1.1.3 4 / 17
1.1.1 5 / 17
1.1.0 5 / 17
1.0.3 2 / 12
1.0.2 2 / 12
1.0.1 2 / 11
1.0.0 2 / 11

v1.1.1

2 findings
HIGH New obfuscated file: dist/YamlProcessor.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH New obfuscated file: dist/YamlProcessor.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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.