@rsbuild/plugin-pug
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.3.3 | 4 / 12 | |
| 1.3.2 | 4 / 12 | |
| 1.3.1 | 4 / 12 | |
| 1.3.0 | 4 / 12 |
v1.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.