@aws/language-server-runtimes-types
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): AWS package publishes via GitHub Actions CI/CD with SLSA attestation; automation-based publisher is expected and stable. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation present; strong supply chain integrity signal for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Type-definitions library; sparse README and no keywords are normal for internal AWS tooling packages. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 0.1.65 | 2 / 0 | |
| 0.1.64 | 2 / 0 | |
| 0.1.63 | 2 / 0 | |
| 0.1.62 | 2 / 0 | |
| 0.1.61 | 2 / 0 | |
| 0.1.60 | 2 / 0 | |
| 0.1.59 | 2 / 0 | |
| 0.1.57 | 2 / 0 | |
| 0.1.56 | 2 / 0 | |
| 0.1.55 | 2 / 0 | |
| 0.1.54 | 2 / 0 | |
| 0.1.53 | 2 / 0 | |
| 0.1.52 | 2 / 0 | |
| 0.1.51 | 2 / 0 | |
| 0.1.50 | 2 / 0 | |
| 0.1.49 | 2 / 0 | |
| 0.1.48 | 2 / 0 | |
| 0.1.47 | 2 / 0 | |
| 0.1.46 | 2 / 0 | |
| 0.1.45 | 2 / 0 | |
| 0.1.44 | 2 / 0 | |
| 0.1.43 | 2 / 0 | |
| 0.1.42 | 2 / 0 | |
| 0.1.41 | 2 / 0 | |
| 0.1.40 | 2 / 0 | |
| 0.1.39 | 2 / 0 | |
| 0.1.38 | 2 / 0 | |
| 0.1.37 | 2 / 0 | |
| 0.1.36 | 2 / 0 | |
| 0.1.35 | 2 / 0 | |
| 0.1.34 | 2 / 0 | |
| 0.1.33 | 2 / 0 | |
| 0.1.32 | 2 / 0 | |
| 0.1.31 | 2 / 0 | |
| 0.1.30 | 2 / 0 | |
| 0.1.29 | 2 / 0 | |
| 0.1.28 | 2 / 0 | |
| 0.1.27 | 2 / 0 | |
| 0.1.26 | 2 / 0 | |
| 0.1.25 | 2 / 0 | |
| 0.1.24 | 2 / 0 | |
| 0.1.23 | 2 / 0 | |
| 0.1.22 | 2 / 0 | |
| 0.1.21 | 2 / 0 | |
| 0.1.20 | 2 / 0 | |
| 0.1.19 | 2 / 0 | |
| 0.1.18 | 2 / 0 | |
| 0.1.17 | 2 / 0 | |
| 0.1.16 | 2 / 0 | |
| 0.1.15 | 2 / 0 | |
| 0.1.14 | 2 / 0 |
v0.1.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.