@universityofmaryland/web-elements-library
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tw-to-css | AI (phantom-deps): Used via build config convention, not direct import; stable pattern for this CSS tooling package. | ai | |
| phantom-deps | phantom-dep:postcss-js | AI (phantom-deps): Framework-scoped CSS tooling dep loaded by convention; stable false positive for this package. | ai | |
| provenance | missing-githead | AI (provenance): Likely a CI/publish environment change for this org; all other signals are clean and publisher is trusted. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are first-party @universityofmaryland/* packages consistent with internal library decomposition. | ai | |
| phantom-deps | phantom-dep:@types/postcss-js | AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.7.2 | 6 / 5 | |
| 1.7.1 | 6 / 5 | |
| 1.7.0 | 6 / 5 | |
| 1.6.17 | 6 / 5 | |
| 1.6.16 | 6 / 5 | |
| 1.6.15 | 6 / 5 | |
| 1.6.14 | 6 / 5 | |
| 1.6.13 | 6 / 5 | |
| 1.6.12 | 6 / 5 | |
| 1.6.11 | 6 / 5 | |
| 1.6.10 | 6 / 5 | |
| 1.6.9 | 2 / 5 | |
| 1.6.8 | 2 / 5 | |
| 1.6.7 | 2 / 5 | |
| 1.6.6 | 2 / 4 | |
| 1.6.5 | 2 / 4 | |
| 1.6.4 | 2 / 4 | |
| 1.6.3 | 2 / 4 | |
| 1.6.2 | 2 / 4 | |
| 1.6.1 | 2 / 4 | |
| 1.6.0 | 2 / 4 | |
| 1.5.9 | 4 / 4 | |
| 1.5.8 | 4 / 4 | |
| 1.5.7 | 4 / 4 | |
| 1.5.6 | 4 / 4 | |
| 1.5.5 | 4 / 4 | |
| 1.5.3 | 1 / 4 | |
| 1.5.2 | 1 / 4 | |
| 1.5.1 | 1 / 4 | |
| 1.5.0 | 1 / 4 | |
| 1.3.7 | 1 / 0 | |
| 1.3.6 | 3 / 0 | |
| 1.3.5 | 3 / 0 | |
| 1.3.4 | 3 / 0 | |
| 1.3.3 | 3 / 0 | |
| 1.3.2 | 3 / 0 | |
| 1.3.1 | 3 / 0 | |
| 1.3.0 | 3 / 0 | |
| 1.2.1 | 3 / 0 | |
| 1.2.0 | 4 / 0 | |
| 1.1.0 | 4 / 0 | |
| 1.0.1 | 3 / 0 | |
| 1.0.0 | 3 / 0 |
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.