@powerlines/plugin-jest
A package containing the Jest testing plugin for Powerlines.
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 minified bundle output from a build tool; code is semantically transparent with no malicious patterns. False positive for this package. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): dist/index.cjs is a standard minified CJS bundle produced by Storm Software's build toolchain; long lines are expected and not obfuscation. Stable false positive for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Version diff shows no material changes to deps/scripts/large files; new files consistent with expanding type exports in a growing plugin package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from stormie-bot to GitHub Actions as part of a CI/CD migration. SLSA provenance attestation confirms builds are produced by the declared workflow, making this a legitimate transition. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): Jest plugin naturally declares jest as dependency but loads it via plugin system; stable for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Utility dependency used indirectly through plugin architecture; stable for this package. | ai | |
| phantom-deps | phantom-dep:jest-util | AI (phantom-deps): Jest framework package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@stryke/path | AI (phantom-deps): Utility dependency used indirectly through plugin architecture; stable for this package. | ai | |
| phantom-deps | phantom-dep:jest-config | AI (phantom-deps): Jest internal dependency; loaded by convention in Jest plugins. | ai | |
| phantom-deps | phantom-dep:powerlines | AI (phantom-deps): Core dependency for Powerlines plugin; referenced in config as expected. | ai | |
| phantom-deps | phantom-dep:@stryke/fs | AI (phantom-deps): Legitimate dependency for filesystem operations in Jest plugin; normal pattern. | ai | |
| phantom-deps | phantom-dep:jest-resolve | AI (phantom-deps): Jest internal dependency; loaded by convention in Jest plugins. | ai | |
| phantom-deps | phantom-dep:@jest/reporters | AI (phantom-deps): Framework-scoped Jest package; loaded by convention as noted by analyzer. | ai | |
| phantom-deps | phantom-dep:@jest/test-result | AI (phantom-deps): Framework-scoped Jest package; loaded by convention as noted by analyzer. | ai | |
| phantom-deps | phantom-dep:defu | AI (phantom-deps): Legitimate dependency for a Jest plugin; referenced in config files as expected. | ai |
Versions (showing 79 of 583)
| Version | Deps | Published |
|---|---|---|
| 0.1.81 | 11 / 3 | |
| 0.1.80 | 11 / 3 | |
| 0.1.79 | 11 / 3 | |
| 0.1.78 | 11 / 3 | |
| 0.1.77 | 11 / 3 | |
| 0.1.76 | 11 / 3 | |
| 0.1.75 | 11 / 3 | |
| 0.1.74 | 11 / 3 | |
| 0.1.73 | 11 / 3 | |
| 0.1.72 | 11 / 3 | |
| 0.1.71 | 11 / 3 | |
| 0.1.70 | 11 / 3 | |
| 0.1.69 | 11 / 3 | |
| 0.1.68 | 11 / 3 | |
| 0.1.67 | 11 / 3 | |
| 0.1.66 | 11 / 3 | |
| 0.1.65 | 11 / 3 | |
| 0.1.64 | 11 / 3 | |
| 0.1.63 | 11 / 3 | |
| 0.1.62 | 11 / 3 | |
| 0.1.61 | 11 / 3 | |
| 0.1.60 | 11 / 3 | |
| 0.1.59 | 11 / 3 | |
| 0.1.58 | 11 / 3 | |
| 0.1.57 | 11 / 3 | |
| 0.1.56 | 11 / 3 | |
| 0.1.55 | 11 / 3 | |
| 0.1.54 | 11 / 3 | |
| 0.1.53 | 11 / 3 | |
| 0.1.52 | 11 / 3 | |
| 0.1.51 | 11 / 3 | |
| 0.1.50 | 11 / 3 | |
| 0.1.49 | 11 / 3 | |
| 0.1.48 | 11 / 3 | |
| 0.1.47 | 11 / 3 | |
| 0.1.46 | 11 / 3 | |
| 0.1.45 | 11 / 3 | |
| 0.1.44 | 11 / 3 | |
| 0.1.43 | 11 / 3 | |
| 0.1.42 | 11 / 3 | |
| 0.1.41 | 11 / 3 | |
| 0.1.40 | 11 / 3 | |
| 0.1.39 | 11 / 3 | |
| 0.1.38 | 11 / 3 | |
| 0.1.37 | 11 / 3 | |
| 0.1.36 | 11 / 3 | |
| 0.1.35 | 11 / 3 | |
| 0.1.34 | 11 / 3 | |
| 0.1.33 | 11 / 3 | |
| 0.1.31 | 11 / 3 | |
| 0.1.30 | 11 / 3 | |
| 0.1.29 | 11 / 3 | |
| 0.1.28 | 11 / 3 | |
| 0.1.27 | 11 / 3 | |
| 0.1.26 | 11 / 3 | |
| 0.1.23 | 11 / 3 | |
| 0.1.22 | 11 / 3 | |
| 0.1.21 | 11 / 3 | |
| 0.1.20 | 11 / 3 | |
| 0.1.19 | 11 / 3 | |
| 0.1.18 | 11 / 3 | |
| 0.1.17 | 11 / 3 | |
| 0.1.16 | 11 / 3 | |
| 0.1.15 | 11 / 3 | |
| 0.1.14 | 11 / 3 | |
| 0.1.13 | 11 / 3 | |
| 0.1.12 | 11 / 3 | |
| 0.1.11 | 11 / 3 | |
| 0.1.10 | 11 / 3 | |
| 0.1.9 | 11 / 3 | |
| 0.1.8 | 11 / 3 | |
| 0.1.7 | 11 / 3 | |
| 0.1.6 | 11 / 3 | |
| 0.1.5 | 11 / 3 | |
| 0.1.4 | 11 / 3 | |
| 0.1.3 | 11 / 3 | |
| 0.1.2 | 11 / 3 | |
| 0.1.1 | 11 / 3 | |
| 0.1.0 | 11 / 3 |
v0.1.80
3 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.1.78
3 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.1.77
3 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.1.76
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.1.74
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.1.73
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.1.72
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.1.71
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.1.69
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.1.67
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.1.61
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.1.57
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.1.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.1.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.1.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.1.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.1.29
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.1.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.1.27
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.1.26
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.1.23
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.1.22
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.1.21
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.1.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.1.19
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.1.18
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.1.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.1.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.1.15
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.1.14
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.1.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.1.12
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.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
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.