typed-event-target
EventTarget in the browser but with strong event typing.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with consistent publisher history; lack of provenance is common and not a security signal here. | ai | |
| phantom-deps | phantom-dep:@augment-vir/core | AI (phantom-deps): Package is from the same author's ecosystem; referenced in config files as expected for a monorepo-style dependency. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.3.2 | 3 / 40 | |
| 4.3.1 | 3 / 40 | |
| 4.3.0 | 3 / 40 | |
| 4.2.0 | 3 / 40 | |
| 4.1.0 | 3 / 40 | |
| 4.0.4 | 3 / 40 | |
| 4.0.3 | 3 / 40 | |
| 4.0.2 | 3 / 40 | |
| 4.0.1 | 2 / 40 | |
| 4.0.0 | 3 / 39 |
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.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.