← Home

@quilted/preact-browser

28
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

lemonmade

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Deps are first-party or well-known SSR lib, fit package purpose. ai
dependencies unvetted-dep:@quilted/request-router AI (dependencies): First-party sibling package from same monorepo/publisher. ai
provenance publisher-changed AI (provenance): Transition from manual (lemonmade) to GitHub Actions CI publishing; SLSA attestation confirms legitimate automated pipeline. ai
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/preact-context AI (dependencies): Same-monorepo sibling dep; stable pattern across all @quilted/* packages. 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
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 28 of 28)

Version Deps Published
0.2.10 6 / 1
0.2.9 6 / 1
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.1 6 / 1
0.2.0 6 / 1
0.1.17 7 / 1
0.1.16 7 / 1
0.1.14 7 / 1
0.1.13 7 / 1
0.1.12 7 / 1
0.1.11 5 / 1
0.1.10 5 / 1
0.1.9 5 / 1
0.1.8 5 / 1
0.1.7 5 / 1
0.1.6 5 / 1
0.1.5 5 / 1
0.1.4 5 / 1
0.1.3 5 / 1
0.1.2 5 / 1
0.1.1 5 / 1
0.1.0 5 / 1

v0.1.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.