@telperion/elements
[](https://badge.fury.io/js/@telperion%2Felements) [](https://www.npmjs.com/package/@telperion/elements)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:iife/popover/index.js | AI (source-diff): Standard minified IIFE bundle output for a Lit web component; matches existing iife/* build pattern for this package. | ai | |
| source-diff | obfuscated-file:iife/router/index.js | AI (source-diff): Standard minified IIFE browser bundle declared in package.json exports; contains recognizable Lit boilerplate. | ai | |
| source-diff | obfuscated-file:iife/icon/index.js | AI (source-diff): Standard minified IIFE browser bundle declared in package.json exports; contains recognizable Lit boilerplate. | ai | |
| source-diff | obfuscated-file:iife/drag-drop/index.js | AI (source-diff): Standard minified IIFE browser bundle declared in package.json exports; contains recognizable Lit boilerplate. | ai | |
| source-diff | obfuscated-file:iife/button/index.js | AI (source-diff): IIFE bundle with source map; standard minified build output for CDN distribution, not obfuscation. | ai | |
| source-diff | obfuscated-file:iife/select/index.js | AI (source-diff): IIFE output is standard minified Lit bundle with accompanying source map; not obfuscation. | ai | |
| dependencies | unvetted-dep:@thalesrc/dom-utils | AI (dependencies): Same author org as this package; consistent with the thalesrc/telperion ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@lit-labs/signals | AI (dependencies): Official Lit Labs experimental package; low risk for a UI component library. | ai | |
| dependencies | unvetted-dep:@telperion/extra-ts-types | AI (dependencies): First-party dep from same org/publisher; consistent across versions. | ai | |
| dependencies | unvetted-dep:@telperion/js-utils | AI (dependencies): First-party dep from same org/publisher; consistent across versions. | ai | |
| dependencies | unvetted-dep:@telperion/dom-utils | AI (dependencies): First-party dep from same org/publisher; consistent across versions. | ai | |
| provenance | no-provenance | AI (provenance): Low-traffic scoped package; absence of provenance is common and not a risk signal here. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 5.3.1 | 8 / 0 | |
| 5.2.0 | 8 / 0 | |
| 5.1.0 | 8 / 0 | |
| 5.0.6 | 8 / 0 | |
| 5.0.5 | 8 / 0 | |
| 5.0.0 | 8 / 0 | |
| 4.2.0 | 8 / 0 | |
| 4.1.0 | 8 / 0 | |
| 4.0.1 | 8 / 0 | |
| 3.0.3 | 7 / 0 | |
| 3.0.1 | 7 / 0 | |
| 3.0.0 | 7 / 0 | |
| 2.0.1 | 7 / 0 | |
| 2.0.0 | 7 / 0 | |
| 1.2.1 | 7 / 0 | |
| 1.2.0 | 7 / 0 | |
| 1.1.2 | 7 / 0 | |
| 1.1.1 | 7 / 0 | |
| 1.1.0 | 7 / 0 | |
| 1.0.0 | 6 / 0 |
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
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.
v5.0.5
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.
v5.0.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.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.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.
v4.0.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.
v3.0.3
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
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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
4 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.