@photo-sphere-viewer/virtual-tour-plugin
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from mistic100 to GitHub Actions CI/CD is confirmed by SLSA provenance attestation on the same repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD pipeline migration; SLSA attestation confirms legitimate publish. | ai | |
| email-domain | unclaimed-email:git.strangeplanet.fr | AI (email-domain): Author's own personal domain (strangeplanet.fr homepage listed); subdomain used for email; stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package; absence of provenance is consistent across all 60 versions and is not a risk signal here. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.15.0 | 0 / 0 | |
| 5.14.3 | 0 / 0 | |
| 5.14.2 | 0 / 0 | |
| 5.14.1 | 0 / 0 | |
| 5.14.0 | 0 / 0 | |
| 5.13.4 | 0 / 0 | |
| 5.13.3 | 0 / 0 | |
| 5.13.2 | 0 / 0 | |
| 5.13.1 | 0 / 0 | |
| 5.12.1 | 0 / 0 | |
| 5.12.0 | 0 / 0 | |
| 5.11.5 | 0 / 0 | |
| 5.11.4 | 0 / 0 | |
| 5.11.3 | 0 / 0 | |
| 5.11.2 | 0 / 0 | |
| 5.11.1 | 0 / 0 | |
| 5.11.0 | 0 / 0 | |
| 5.10.1 | 0 / 0 | |
| 5.10.0 | 0 / 0 | |
| 5.9.0 | 0 / 0 | |
| 5.8.3 | 0 / 0 | |
| 5.8.2 | 0 / 0 | |
| 5.8.1 | 0 / 0 | |
| 5.8.0 | 0 / 0 | |
| 5.7.4 | 0 / 0 |
v5.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.