@a2ui/lit
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@lit-labs/signals | AI (phantom-deps): Same barrel/re-export pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:lit | AI (phantom-deps): Library re-exports lit ecosystem deps via barrel/config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lit/context | AI (phantom-deps): Same barrel/re-export pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:signal-utils | AI (phantom-deps): Same barrel/re-export pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@a2ui/web_core | AI (phantom-deps): Same org scope; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @a2ui/lit; edit-distance match to 'got' is a false positive with no impersonation intent. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown parser; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@lit-labs/signals | AI (dependencies): @lit-labs/signals is an official Lit Labs package from the Lit team; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @a2ui/lit; edit-distance match to 'vite' is a false positive with no impersonation intent. | ai |
v0.9.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: a2ui-team.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.