← Home

@rsbuild/plugin-pug

npm Repository Homepage
10
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

chenjiahanhardfist3

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Likely org-internal maintainer rename; still CI/CD attested publish. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with maintainer-added, consistent with rename not takeover. ai
provenance missing-githead AI (provenance): CI tooling variance; provenance attestation still present and unchanged direction. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate pipeline change for rspack-contrib org. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI-attested publish; SLSA provenance confirms legitimate release pipeline. ai
phantom-deps phantom-dep:@types/pug AI (phantom-deps): Type-only dependency; framework-scoped, not directly imported at runtime. ai

Versions (showing 10 of 10)

Version Deps Published
2.0.0 4 / 13
1.3.4 4 / 12
1.3.3 4 / 12
1.3.2 4 / 12
1.3.1 4 / 12
1.3.0 4 / 12
1.2.0 4 / 12
1.1.0 3 / 11
1.0.2 3 / 11
1.0.1 3 / 11

v2.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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

1 finding
LOW No provenance attestation provenance

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

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