← Home

eslint-plugin-anti-trojan-source

ESLint plugin to detect and stop Trojan Source attacks

14
Versions
Apache-2.0
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

lirantallirantal_bot

Keywords

eslinteslint-plugineslintpluginplugineslint pluginrulestrojantrojan sourcesourceunicodebidibidirectional attacksbidi attacksbidi securityunicode securityattackssecurity

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:anti-trojan-source AI (dependencies): anti-trojan-source is the intentional core dependency this plugin wraps; stable relationship across all versions. ai

Versions (showing 14 of 14)

Version Deps Published
1.1.6 1 / 8
1.1.5 1 / 8
1.1.4 1 / 8
1.1.3 1 / 8
1.1.2 1 / 8
1.1.1 1 / 8
1.1.0 1 / 8
1.0.6 1 / 8
1.0.5 1 / 8
1.0.4 1 / 8
1.0.3 1 / 7
1.0.2 1 / 7
1.0.1 1 / 7
1.0.0 1 / 7

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.