@glodon-aiot/apis
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@glodon-aiot/minio | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled/re-exported org packages. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped org package @glodon-aiot/apis; not a typosquat of hapi — edit distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:axios | AI (typosquat): Scoped org package @glodon-aiot/apis; not a typosquat of axios — edit distance match is coincidental. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 4 / 34 | |
| 3.15.0 | 4 / 34 | |
| 3.11.0 | 4 / 34 | |
| 3.9.1 | 4 / 34 | |
| 3.9.0 | 4 / 34 | |
| 3.8.0 | 4 / 34 | |
| 3.6.2 | 4 / 34 | |
| 3.4.3 | 4 / 34 | |
| 3.4.0 | 4 / 34 | |
| 3.3.6 | 4 / 34 | |
| 3.3.1 | 4 / 34 | |
| 3.0.8 | 3 / 32 | |
| 3.0.7 | 3 / 32 | |
| 3.0.6 | 3 / 32 | |
| 3.0.5 | 3 / 32 |
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.