@quilted/preact-browser
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has clean track record; no material changes vs prior version; part of established quilted monorepo. | ai | |
| dependencies | unvetted-dep:@quilted/http | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @quilted/* packages. | ai | |
| dependencies | unvetted-dep:@quilted/assets | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @quilted/* packages. | ai | |
| dependencies | unvetted-dep:@quilted/signals | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @quilted/* packages. | ai | |
| dependencies | unvetted-dep:@quilted/preact-context | AI (dependencies): Same-monorepo sibling dep; stable pattern across all @quilted/* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is cosmetic, not a risk signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README/metadata is typical for internal monorepo packages; not a spam/malware indicator for this publisher. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.8 | 6 / 1 | |
| 0.2.7 | 6 / 1 | |
| 0.2.6 | 6 / 1 | |
| 0.2.5 | 6 / 1 | |
| 0.2.4 | 6 / 1 | |
| 0.2.3 | 6 / 1 | |
| 0.2.2 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.17 | 7 / 1 |
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.