@appland/rpc
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @appland package; Levenshtein match to 'pg' is coincidental, no impersonation intent. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.22.0 | 1 / 4 | |
| 1.21.0 | 1 / 4 | |
| 1.20.0 | 1 / 4 | |
| 1.19.0 | 1 / 4 | |
| 1.18.0 | 1 / 4 | |
| 1.17.0 | 1 / 4 | |
| 1.16.0 | 0 / 4 | |
| 1.15.0 | 0 / 4 | |
| 1.14.0 | 0 / 4 | |
| 1.13.0 | 0 / 4 | |
| 1.12.0 | 0 / 4 | |
| 1.11.0 | 0 / 4 | |
| 1.10.0 | 0 / 4 | |
| 1.9.0 | 0 / 4 | |
| 1.8.0 | 0 / 4 | |
| 1.7.0 | 0 / 4 | |
| 1.6.0 | 0 / 4 | |
| 1.5.0 | 0 / 4 | |
| 1.4.0 | 0 / 4 | |
| 1.3.0 | 0 / 4 | |
| 1.2.0 | 0 / 4 | |
| 1.1.1 | 0 / 4 | |
| 1.1.0 | 0 / 4 | |
| 1.0.0 | 0 / 4 |
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.