@socket.tech/ll-common
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pg | AI (phantom-deps): pg is a declared runtime dep used via typeorm/pg-native; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:pg-native | AI (phantom-deps): pg-native is a platform-specific binary dep; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@middy/core | AI (phantom-deps): Lambda middleware loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/rds-signer | AI (phantom-deps): Framework-scoped AWS SDK package loaded by convention in Lambda context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org library; missing metadata (no description, no repo URL) is consistent across all 168 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all versions of this internal library. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.0.118 | 16 / 35 | |
| 0.0.115 | 16 / 35 | |
| 0.0.112 | 16 / 35 | |
| 0.0.110 | 16 / 35 | |
| 0.0.108 | 16 / 35 | |
| 0.0.107 | 16 / 35 | |
| 0.0.106 | 16 / 35 | |
| 0.0.105 | 16 / 35 | |
| 0.0.103 | 16 / 35 | |
| 0.0.102 | 16 / 35 | |
| 0.0.101 | 16 / 35 | |
| 0.0.100 | 16 / 35 | |
| 0.0.99 | 16 / 35 | |
| 0.0.98 | 16 / 35 |
v0.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.