@teamwork/vue-dropdown-directive
A vue.js directive for handling dropdowns
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/js/chunk-vendors.06ec4b47.js | AI (source-diff): Webpack vendor chunk bundler output, not a loader. | ai | |
| source-diff | net-exec-file:dist/js/app-legacy.7b54c396.js | AI (source-diff): Webpack bundle; pattern match on minified code, no real dropper behavior. | ai | |
| source-diff | net-exec-file:dist/js/app.5630803d.js | AI (source-diff): Webpack bundle; pattern match on minified code, no real dropper behavior. | ai | |
| source-diff | net-exec-file:dist/js/chunk-vendors-legacy.e9461ab9.js | AI (source-diff): Webpack vendor chunk bundler output, not a loader. | ai | |
| source-diff | obfuscated-file:dist/js/app-legacy.7b54c396.js | AI (source-diff): Standard vue-cli-service minified build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/js/app.5630803d.js | AI (source-diff): Standard vue-cli-service minified build output, not true obfuscation. | ai | |
| phantom-deps | phantom-dep:debounce | AI (phantom-deps): Debounce is a runtime utility dependency; stable across versions. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Core-js is a polyfill dependency; implicit runtime usage is expected. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a runtime dependency for this directive; phantom-dep heuristic doesn't capture framework peer patterns. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.7 | 3 / 13 | |
| 3.0.6 | 3 / 13 | |
| 3.0.5 | 3 / 13 | |
| 3.0.4 | 3 / 13 | |
| 3.0.2 | 3 / 13 | |
| 3.0.1 | 3 / 13 | |
| 3.0.0 | 3 / 13 |
v3.0.6
8 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bradderz) than the most recent previously approved version (ma-jerez) on 2025-03-27, but bradderz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ma-jerez) than the most recent previously approved version (bradderz) on 2024-08-23, but ma-jerez is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.