← Home

@fenge/eslint-plugin-ts

npm Repository Homepage
20
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

zanminkian

Keywords

stricteslintplugineslint-plugintypescriptunicorn

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/rules/no-misuse-spreading-parameter.js AI (source-diff): Long line is a sourcemap base64 comment, not obfuscated code; source is plain compiled TS. ai
publish-pattern new-deps-added AI (publish-pattern): Adds well-known @typescript-eslint/utils dependency; benign. ai
provenance publisher-changed AI (provenance): Transition from manual publish (zanminkian) to GitHub Actions CI/CD is consistent with SLSA attestation and repo ownership. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD-attested publish with matching repo URL; low takeover risk given SLSA provenance. ai

Versions (showing 20 of 20)

Version Deps Published
0.5.1 1 / 4
0.5.0 1 / 4
0.4.11 1 / 4
0.4.10 1 / 4
0.4.9 1 / 4
0.4.8 1 / 4
0.4.7 1 / 4
0.4.6 1 / 4
0.4.5 1 / 4
0.4.4 1 / 4
0.4.3 1 / 4
0.4.2 1 / 4
0.4.1 1 / 4
0.4.0 1 / 5
0.3.0 1 / 5
0.2.3 1 / 5
0.2.2 1 / 6
0.2.1 1 / 6
0.2.0 0 / 6
0.1.0 0 / 6

v0.4.0

2 findings
HIGH New obfuscated file: dist/rules/no-misuse-spreading-parameter.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.

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.

v0.3.0

2 findings
HIGH New obfuscated file: dist/rules/no-misuse-spreading-parameter.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.

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.

v0.2.3

2 findings
HIGH New obfuscated file: dist/rules/no-misuse-spreading-parameter.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.

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.

v0.2.2

2 findings
HIGH New obfuscated file: dist/rules/no-misuse-spreading-parameter.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.

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.

v0.2.1

2 findings
HIGH New obfuscated file: dist/rules/no-misuse-spreading-parameter.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.

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.

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.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.