← Home

@trapar-waves/vue-tailwind

npm Repository Homepage

A Vue 3 project template integrated with Tailwind CSS for rapid frontend development

9
Versions
MIT
License
Yes
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

muromi

Keywords

vuevue3tailwindcsstypescriptrsbuildeslinticonify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): postinstall runs 'husky' for git hooks setup; standard dev tooling pattern, stable for this package. ai
phantom-deps phantom-dep:@vueuse/core AI (phantom-deps): @vueuse/core is a declared runtime dependency; phantom-dep heuristic is a false positive here. ai

Versions (showing 9 of 9)

Version Deps Published
1.2.0 2 / 15
1.1.17 2 / 12
1.1.0 2 / 12
1.0.5 2 / 10
1.0.4 2 / 10
1.0.3 2 / 10
1.0.2 2 / 10
1.0.1 2 / 10
1.0.0 2 / 10

v1.1.17

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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.

v1.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.

v1.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.