@universityofmaryland/web-components-library
UMD Web Components
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cdn.js | AI (source-diff): Minified Vite bundle output; sample confirms legitimate UI component code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:jest-dom | AI (phantom-deps): Test tooling referenced in config only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:postcss-nesting | AI (phantom-deps): Build-time PostCSS plugin referenced in config; not a direct runtime import. | ai | |
| phantom-deps | phantom-dep:tw-to-css | AI (phantom-deps): Referenced in build config files, not a runtime import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@universityofmaryland/web-builder-library | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@types/postcss-js | AI (phantom-deps): Type-only package; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:postcss-js | AI (phantom-deps): Build-time CSS tooling referenced in config; not a direct runtime import. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.18.10 | 12 / 6 | |
| 1.18.6 | 12 / 6 | |
| 1.18.4 | 12 / 6 | |
| 1.18.2 | 12 / 6 | |
| 1.12.24 | 2 / 0 | |
| 1.12.6 | 4 / 0 | |
| 1.11.9 | 4 / 0 | |
| 1.10.4 | 3 / 0 | |
| 1.10.2 | 3 / 0 | |
| 1.10.1 | 3 / 0 |
v1.18.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: magnessjo.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.