@interopio/ng
IO Connect library for Angular - Browser and Desktop
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
Keywords
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 @interopio/ng is a legitimate Angular library; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same rationale; 2-edit distance to 'qs' is coincidental for this established scoped package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 0 / 1 | |
| 6.2.0 | 0 / 1 | |
| 6.1.5 | 3 / 0 | |
| 6.1.4 | 3 / 0 | |
| 6.1.3 | 3 / 0 | |
| 6.1.2 | 3 / 0 | |
| 6.1.1 | 3 / 0 | |
| 6.1.0 | 3 / 0 | |
| 6.0.6 | 3 / 0 | |
| 6.0.5 | 3 / 0 | |
| 6.0.4 | 3 / 0 | |
| 6.0.3 | 3 / 0 | |
| 6.0.2 | 3 / 0 | |
| 6.0.1 | 3 / 0 | |
| 6.0.0 | 3 / 0 |
v6.3.0
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
2 findingsPackage name '@interopio/ng' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.