@powerlines/plugin-eslint
A package containing a Powerlines plugin for running ESLint on the codebase.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): dist/index.mjs is standard tsup-minified build output; code is readable and benign. SLSA provenance confirms CI/CD build pipeline. Stable false positive for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently publishes with SLSA provenance via Sigstore; strong supply chain integrity signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Storm Software transitioned from stormie-bot to GitHub Actions CI publishing. SLSA provenance attestation confirms legitimate CI/CD pipeline. This transition is stable for the package going forward. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): dist/index.cjs is standard tsup-bundled/minified CJS output for a build tool plugin. Long lines are a bundling artifact, not obfuscation. Content is readable and benign. | ai | |
| phantom-deps | phantom-dep:powerlines | AI (phantom-deps): Core framework dependency for powerlines plugin; used indirectly by plugin system. | ai | |
| phantom-deps | phantom-dep:@stryke/path | AI (phantom-deps): Utility dependency used indirectly by plugin framework; legitimate for this package's architecture. | ai | |
| phantom-deps | phantom-dep:defu | AI (phantom-deps): Plugin package; defu is a legitimate config utility dependency used indirectly by the plugin framework. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): ESLint plugin; eslint is a peer/framework dependency used indirectly; standard pattern for ESLint plugins. | ai | |
| phantom-deps | phantom-dep:@stryke/fs | AI (phantom-deps): Utility dependency used indirectly by plugin framework; legitimate for this package's architecture. | ai | |
| phantom-deps | phantom-dep:@storm-software/config-tools | AI (phantom-deps): Used in config files rather than direct imports; this is a known pattern for config-tools packages in monorepos. Not a security concern for this package. | ai |
Versions (showing 49 of 361)
| Version | Deps | Published |
|---|---|---|
| 0.8.36 | 6 / 3 | |
| 0.8.35 | 6 / 3 | |
| 0.8.34 | 6 / 3 | |
| 0.8.33 | 6 / 3 | |
| 0.8.32 | 6 / 3 | |
| 0.8.31 | 6 / 3 | |
| 0.8.30 | 6 / 3 | |
| 0.8.28 | 6 / 3 | |
| 0.8.27 | 6 / 3 | |
| 0.8.26 | 6 / 3 | |
| 0.8.25 | 6 / 3 | |
| 0.8.24 | 6 / 3 | |
| 0.8.23 | 6 / 3 | |
| 0.8.20 | 6 / 3 | |
| 0.8.19 | 6 / 3 | |
| 0.8.18 | 6 / 3 | |
| 0.8.17 | 6 / 3 | |
| 0.8.16 | 6 / 3 | |
| 0.8.15 | 6 / 3 | |
| 0.8.14 | 6 / 3 | |
| 0.8.13 | 6 / 3 | |
| 0.8.12 | 6 / 3 | |
| 0.8.11 | 6 / 3 | |
| 0.8.10 | 6 / 3 | |
| 0.8.9 | 6 / 3 | |
| 0.8.8 | 6 / 3 | |
| 0.8.7 | 6 / 3 | |
| 0.8.6 | 6 / 3 | |
| 0.8.5 | 6 / 3 | |
| 0.8.4 | 6 / 3 | |
| 0.8.3 | 6 / 3 | |
| 0.8.2 | 6 / 3 | |
| 0.8.1 | 6 / 3 | |
| 0.8.0 | 6 / 3 | |
| 0.7.3 | 6 / 3 | |
| 0.7.2 | 6 / 3 | |
| 0.7.1 | 6 / 3 | |
| 0.7.0 | 6 / 3 | |
| 0.6.3 | 6 / 3 | |
| 0.6.2 | 6 / 3 | |
| 0.6.1 | 6 / 3 | |
| 0.6.0 | 6 / 3 | |
| 0.5.0 | 6 / 3 | |
| 0.4.1 | 6 / 3 | |
| 0.4.0 | 6 / 3 | |
| 0.3.0 | 6 / 3 | |
| 0.2.0 | 6 / 3 | |
| 0.1.1 | 6 / 3 | |
| 0.1.0 | 6 / 3 |
v0.8.36
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.34
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.33
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.32
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.31
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.30
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.28
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.20
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.17
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.16
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.13
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.11
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.9
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.