@highstate/yandex-sdk
A Pulumi provider dynamically bridged from yandex.
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 | missing-githead | AI (provenance): Package has SLSA provenance attestation via Sigstore, which supersedes gitHead as a supply chain integrity signal. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Pulumi parameterized provider SDK; postinstall fetches/configures the bridged provider binary, standard pattern for this package family. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Pulumi resource constructor pattern; not dynamic code compilation from user input. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build-time dependency used by tsc; not imported at runtime. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type definitions only; loaded by convention, not directly imported. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.19.1 | 4 / 0 | |
| 0.14.0 | 4 / 0 | |
| 0.13.2 | 4 / 0 | |
| 0.13.1 | 4 / 0 | |
| 0.13.0 | 4 / 0 | |
| 0.12.1 | 4 / 0 | |
| 0.12.0 | 4 / 0 | |
| 0.11.7 | 4 / 0 | |
| 0.11.6 | 4 / 0 | |
| 0.11.5 | 4 / 0 | |
| 0.11.4 | 4 / 0 | |
| 0.11.3 | 4 / 0 | |
| 0.10.0 | 4 / 1 | |
| 0.9.37 | 4 / 1 | |
| 0.9.36 | 4 / 1 | |
| 0.9.35 | 4 / 1 | |
| 0.9.34 | 4 / 1 | |
| 0.9.33 | 4 / 1 | |
| 0.9.32 | 4 / 1 | |
| 0.9.31 | 4 / 1 | |
| 0.9.30 | 4 / 1 | |
| 0.9.29 | 4 / 1 | |
| 0.9.28 | 4 / 1 | |
| 0.9.27 | 4 / 1 | |
| 0.9.26 | 4 / 1 | |
| 0.9.25 | 4 / 1 | |
| 0.9.24 | 4 / 1 | |
| 0.9.23 | 4 / 1 | |
| 0.9.22 | 4 / 1 | |
| 0.9.21 | 4 / 1 | |
| 0.9.20 | 4 / 1 |
v0.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.1
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: exeteres.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: exeteres.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: exeteres.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.22
2 findingsScript: node ./scripts/postinstall.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
2 findingsScript: node ./scripts/postinstall.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.20
2 findingsScript: node ./scripts/postinstall.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.