@warp-ds/elements
Custom elements for Warp
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/packages/attention/attention.js | AI (source-diff): Bundled/minified build output from esbuild/rollup, not obfuscation. | ai | |
| dependencies | unvetted-dep:@warp-ds/components | AI (dependencies): First-party sibling package in the same monorepo/org. | ai | |
| source-diff | obfuscated-file:dist/packages/affix/affix.js | AI (source-diff): Bundled esbuild output, not true obfuscation; matches build pipeline. | ai | |
| source-diff | obfuscated-file:dist/packages/switch/index.js | AI (source-diff): esbuild-bundled minified output, not true obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): lit is a well-known, standard web-components dependency. | ai | |
| source-diff | obfuscated-file:dist/packages/combobox/index.js | AI (source-diff): esbuild-bundled minified output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/packages/datepicker/index.js | AI (source-diff): esbuild-bundled minified output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/packages/datepicker/datepicker.js | AI (source-diff): Minified rollup/esbuild bundle output, not true obfuscation; matches documented build pipeline. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Bundling previously-external deps inline explains the new file count; no malicious content found. | ai | |
| source-diff | obfuscated-file:dist/packages/snackbar/snackbar.js | AI (source-diff): dist/ files are expected minified rollup/terser build artifacts for this package. | ai | |
| source-diff | obfuscated-file:eik/index.js | AI (source-diff): eik/index.js is the standard minified bundle entry point for this design-system package; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-node-resolve | AI (phantom-deps): Framework-scoped rollup plugin loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Common implicit runtime dep for TypeScript output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): Build tool referenced in config files; not a runtime import concern. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Referenced in config/build files; expected pattern for this component library. | ai | |
| phantom-deps | phantom-dep:@warp-ds/css | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:scroll-doctor | AI (phantom-deps): Referenced in config files; expected build pattern. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-terser | AI (phantom-deps): Framework-scoped rollup plugin loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-replace | AI (phantom-deps): Framework-scoped rollup plugin loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@warp-ds/elements-core | AI (phantom-deps): Same-org dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-commonjs | AI (phantom-deps): Framework-scoped rollup plugin loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lit-labs/rollup-plugin-minify-html-literals | AI (phantom-deps): Build plugin referenced in config; stable false positive for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently publishes with SLSA provenance attestation via CI. | ai | |
| provenance | publisher-changed | AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA provenance; this is the expected new publisher going forward. | ai | |
| provenance | no-provenance | AI (provenance): Established warp-ds org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.11.0 | 3 / 69 | |
| 2.10.0 | 3 / 69 | |
| 2.9.1 | 3 / 70 | |
| 2.9.0 | 3 / 69 | |
| 2.8.1 | 3 / 71 | |
| 2.8.0 | 3 / 71 | |
| 2.5.1 | 3 / 71 | |
| 2.4.0 | 2 / 71 | |
| 2.3.2 | 2 / 71 | |
| 2.3.1 | 2 / 71 | |
| 2.3.0 | 2 / 71 | |
| 2.2.1 | 16 / 58 | |
| 2.2.0 | 16 / 58 | |
| 2.1.1 | 6 / 31 | |
| 2.0.2 | 6 / 30 | |
| 2.0.1 | 6 / 30 | |
| 2.0.0 | 6 / 30 |
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
12 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
16 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
5 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.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (imprashast) than the most recent previously approved version (balbuhhha) on 2024-12-17, but imprashast 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.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.