← Home

prettier-plugin-svelte

npm Repository Homepage
29
Versions
—
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

conduitrydummdidumm

Keywords

prettiersvelte

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from individual maintainer to GitHub Actions CI/CD; SLSA attestation confirms legitimate publish. ai
provenance missing-githead AI (provenance): Expected when switching to GitHub Actions publish workflow. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer list cleanup during CI/CD migration for official sveltejs org package. ai
semgrep semgrep:base64-decode AI (semgrep): Used for source map decoding in browser bundle; not a malicious payload pattern. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads user-specified svelte5CompilerPath option; documented plugin behavior, not arbitrary code loading. ai

Versions (showing 29 of 29)

Version Deps Published
4.1.1 0 / 14
4.1.0 0 / 14
4.0.1 0 / 14
4.0.0 0 / 14
3.5.2 0 / 12
3.5.1 0 / 12
3.5.0 0 / 12
3.4.1 0 / 12
3.4.0 0 / 12
3.3.3 0 / 12
3.3.2 0 / 12
3.3.1 0 / 12
3.3.0 0 / 12
3.2.8 0 / 12
3.2.7 0 / 12
3.2.6 0 / 12
3.2.5 0 / 12
3.2.4 0 / 12
3.2.3 0 / 12
3.2.2 0 / 12
3.2.1 0 / 12
3.2.0 0 / 12
3.1.2 0 / 11
3.1.1 0 / 11
3.1.0 0 / 11
3.0.3 0 / 11
3.0.2 0 / 11
3.0.1 0 / 11
3.0.0 0 / 11

v3.3.3

1 finding
LOW No provenance attestation provenance

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

v3.3.2

1 finding
LOW No provenance attestation provenance

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

v3.3.1

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.8

1 finding
LOW No provenance attestation provenance

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

v3.2.7

1 finding
LOW No provenance attestation provenance

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

v3.2.6

1 finding
LOW No provenance attestation provenance

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

v3.2.5

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.

v3.2.4

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.

v3.2.3

1 finding
LOW No provenance attestation provenance

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

v3.2.2

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

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.

v3.0.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.