@aws-sdk/endpoint-cache
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist-cjs/EndpointCache.js | AI (source-diff): Readable TSC compiler output, false positive on line length. | ai | |
| source-diff | obfuscated-file:dist-es/EndpointCache.js | AI (source-diff): Readable TSC compiler output, false positive on line length. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 3.972.9 | 2 / 6 | |
| 3.972.8 | 2 / 6 | |
| 3.972.7 | 2 / 6 | |
| 3.972.6 | 2 / 6 | |
| 3.972.5 | 2 / 6 | |
| 3.972.4 | 2 / 6 | |
| 3.972.3 | 2 / 6 | |
| 3.972.2 | 2 / 6 | |
| 3.972.1 | 2 / 6 | |
| 3.972.0 | 2 / 6 | |
| 3.971.0 | 2 / 6 | |
| 3.968.0 | 2 / 6 | |
| 3.965.0 | 2 / 6 | |
| 3.957.0 | 2 / 6 | |
| 3.953.0 | 2 / 6 | |
| 3.893.0 | 2 / 6 | |
| 3.873.0 | 2 / 6 | |
| 3.804.0 | 2 / 6 | |
| 3.723.0 | 2 / 6 | |
| 3.693.0 | 2 / 6 | |
| 3.679.0 | 2 / 6 | |
| 3.678.0 | 2 / 6 | |
| 3.572.0 | 2 / 6 | |
| 3.568.0 | 2 / 6 | |
| 3.567.0 | 2 / 6 | |
| 3.535.0 | 2 / 6 | |
| 3.495.0 | 2 / 6 | |
| 3.465.0 | 2 / 6 | |
| 3.310.0 | 2 / 7 | |
| 3.303.0 | 2 / 7 | |
| 3.295.0 | 2 / 7 | |
| 3.292.0 | 2 / 7 | |
| 3.208.0 | 2 / 7 | |
| 3.201.0 | 2 / 7 | |
| 3.188.0 | 2 / 7 | |
| 3.186.0 | 2 / 7 | |
| 3.183.0 | 2 / 7 | |
| 3.170.0 | 2 / 7 | |
| 3.168.0 | 2 / 7 | |
| 3.55.0 | 2 / 7 | |
| 3.52.0 | 2 / 7 | |
| 3.49.0 | 2 / 7 | |
| 3.47.1 | 2 / 1 | |
| 3.47.0 | 2 / 1 | |
| 3.46.0 | 2 / 1 | |
| 3.36.0 | 2 / 4 | |
| 3.35.0 | 2 / 4 | |
| 3.34.0 | 2 / 4 | |
| 3.32.0 | 2 / 4 | |
| 3.29.0 | 2 / 4 | |
| 3.23.0 | 2 / 4 |
v3.972.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.723.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.693.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.679.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.678.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.572.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.568.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.567.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.535.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.495.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.465.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.310.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.303.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.295.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.292.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.208.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.201.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.188.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.186.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.183.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.170.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.168.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.