@stencil/vue-output-target
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): Ionic/StencilJS org transitioned to GitHub Actions CI publishing with SLSA attestation; stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active development continued on GitHub; gap reflects npm release cadence, not abandonment or takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers gm-os and johnny.jenkins are consistent with Ionic org team expansion; SLSA provenance confirms CI-controlled publish. | ai | |
| provenance | slsa-provenance | AI (provenance): Official Ionic/StencilJS CI pipeline; SLSA attestation is stable for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 0 / 12 | |
| 0.13.1 | 0 / 12 | |
| 0.13.0 | 0 / 12 | |
| 0.12.2 | 0 / 12 | |
| 0.12.1 | 0 / 12 | |
| 0.12.0 | 0 / 9 | |
| 0.11.8 | 0 / 9 | |
| 0.10.8 | 0 / 9 |
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. 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.
v0.12.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. 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.
v0.12.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. 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.
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. 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.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.