@supernovaio/sdk
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:abab | AI (phantom-deps): Declared in dependencies; used by SDK utilities. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared in dependencies; used by SDK utilities. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in dependencies; used by SDK utilities. | ai | |
| phantom-deps | phantom-dep:color2k | AI (phantom-deps): Declared in dependencies; used by SDK color utilities. | ai | |
| phantom-deps | phantom-dep:tinycolor2 | AI (phantom-deps): Declared in dependencies; used by SDK color utilities. | ai | |
| phantom-deps | phantom-dep:async-mutex | AI (phantom-deps): Declared in dependencies; used by SDK utilities. | ai | |
| phantom-deps | phantom-dep:parse-color | AI (phantom-deps): Declared in dependencies; used by SDK color utilities. | ai | |
| phantom-deps | phantom-dep:color-string | AI (phantom-deps): Declared in dependencies; used by SDK color utilities. | ai | |
| phantom-deps | phantom-dep:string.prototype.matchall | AI (phantom-deps): Declared in dependencies; used by SDK utilities. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.4.4 | 11 / 16 | |
| 2.4.3 | 11 / 16 | |
| 2.4.2 | 11 / 16 | |
| 2.4.1 | 11 / 16 | |
| 2.4.0 | 11 / 16 | |
| 2.3.4 | 11 / 16 | |
| 2.3.3 | 12 / 15 |
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jiritrecak) than the most recent previously approved version (GitHub Actions) on 2026-06-02, but jiritrecak is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.