← Home

@terajs/vite-plugin

npm Repository Homepage

Vite plugin for Terajs SFC compilation, route manifest generation, and dev integration.

9
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

thecodergabe

Keywords

terajsvitepluginsfcroutinglocal-first

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@terajs/router AI (phantom-deps): Same-org package; likely used indirectly via re-exports or optional paths within the terajs ecosystem. ai
phantom-deps phantom-dep:@terajs/compiler AI (phantom-deps): Same-org package; indirect usage pattern consistent with terajs monorepo structure. ai
phantom-deps phantom-dep:@terajs/devtools AI (phantom-deps): Same-org package; indirect usage pattern consistent with terajs monorepo structure. ai

Versions (showing 9 of 9)

Version Deps Published
1.1.8 7 / 0
1.1.7 7 / 0
1.1.6 7 / 0
1.1.1 7 / 0
1.0.5 7 / 0
1.0.3 7 / 0
1.0.2 7 / 0
1.0.1 7 / 0
1.0.0 7 / 0

v1.1.8

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

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

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

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.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.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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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.