@symbo.ls/atoms
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:@symbo.ls/emotion | AI (phantom-deps): Same org-scoped dependency; likely used transitively or indirectly within the @symbo.ls ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package; missing metadata is a consistent pattern across the @symbo.ls namespace, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:smbls | AI (phantom-deps): smbls is a same-ecosystem dependency used via config; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 51 of 96)
| Version | Deps | Published |
|---|---|---|
| 3.7.3 | 3 / 1 | |
| 3.7.0 | 3 / 1 | |
| 3.6.8 | 3 / 1 | |
| 3.6.7 | 3 / 1 | |
| 3.6.6 | 3 / 1 | |
| 3.6.4 | 3 / 1 | |
| 3.6.3 | 3 / 1 | |
| 3.6.1 | 3 / 1 | |
| 3.5.1 | 4 / 1 | |
| 3.5.0 | 4 / 1 | |
| 3.4.11 | 4 / 1 | |
| 3.4.9 | 4 / 1 | |
| 3.4.6 | 4 / 1 | |
| 3.4.5 | 4 / 1 | |
| 3.4.4 | 4 / 1 | |
| 3.4.3 | 4 / 1 | |
| 3.4.2 | 4 / 1 | |
| 3.4.1 | 4 / 1 | |
| 3.4.0 | 4 / 1 | |
| 3.3.7 | 4 / 1 | |
| 3.3.5 | 4 / 1 | |
| 3.3.4 | 4 / 1 | |
| 3.3.2 | 4 / 1 | |
| 3.2.3 | 4 / 1 | |
| 2.34.35 | 4 / 1 | |
| 2.34.34 | 4 / 1 | |
| 2.34.33 | 4 / 1 | |
| 2.34.32 | 4 / 1 | |
| 2.34.31 | 4 / 1 | |
| 2.34.30 | 4 / 1 | |
| 2.34.29 | 4 / 1 | |
| 2.34.27 | 4 / 1 | |
| 2.34.25 | 4 / 1 | |
| 2.34.24 | 4 / 1 | |
| 2.34.23 | 4 / 1 | |
| 2.34.22 | 4 / 1 | |
| 2.34.21 | 4 / 1 | |
| 2.34.20 | 4 / 1 | |
| 2.34.18 | 4 / 1 | |
| 2.34.17 | 4 / 1 | |
| 2.34.16 | 4 / 1 | |
| 2.34.15 | 4 / 1 | |
| 2.34.14 | 4 / 1 | |
| 2.34.13 | 4 / 1 | |
| 2.34.12 | 4 / 1 | |
| 2.34.11 | 4 / 1 | |
| 2.34.10 | 4 / 1 | |
| 2.34.9 | 4 / 1 | |
| 2.34.8 | 4 / 1 | |
| 2.34.7 | 4 / 1 | |
| 2.34.6 | 4 / 1 |
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
2 findingsMaintainer email '[email protected]' uses domain 'mvprojects.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.