@upstash/vector
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): Legitimate internal Upstash maintainer transition, repo unchanged. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer rotation within same org, no compromise indicators. | ai | |
| source-diff | obfuscated-file:dist/cloudflare.js | AI (source-diff): tsup/esbuild minified bundle, not true obfuscation; benign HTTP client code. | ai | |
| source-diff | obfuscated-file:dist/nodejs.js | AI (source-diff): tsup/esbuild minified bundle, not true obfuscation; benign HTTP client code. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Team transition within official upstash org, no malicious diff. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 0 / 11 | |
| 1.2.2 | 0 / 11 | |
| 1.2.1 | 0 / 11 | |
| 1.2.0 | 0 / 11 | |
| 1.1.7 | 0 / 11 | |
| 1.1.6 | 0 / 11 | |
| 1.1.5 | 0 / 8 | |
| 1.1.4 | 0 / 8 | |
| 1.1.3 | 0 / 8 | |
| 1.1.2 | 0 / 8 | |
| 1.1.1 | 0 / 8 | |
| 1.1.0 | 0 / 8 | |
| 1.0.7 | 0 / 8 | |
| 1.0.6 | 0 / 8 | |
| 1.0.5 | 0 / 8 | |
| 1.0.4 | 0 / 8 | |
| 1.0.3 | 0 / 8 | |
| 1.0.2 | 0 / 7 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 |
v1.2.1
2 findingsThis version was published by a different npm account than previous versions on 2025-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
2 findingsThis version was published by a different npm account than previous versions on 2024-10-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
4 findingsThis version was published by a different npm account than previous versions on 2024-09-12. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.
v1.1.5
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.
v1.1.4
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.
v1.1.3
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.
v1.1.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.