@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, so a manually published version cannot be tied back to a reviewed commit.
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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.4.8 | 11 / 16 | |
| 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.10 | 11 / 16 | |
| 2.3.9 | 11 / 17 | |
| 2.3.4 | 11 / 16 | |
| 2.3.3 | 12 / 15 | |
| 2.3.2 | 12 / 16 | |
| 2.3.1 | 12 / 16 | |
| 2.2.54 | 12 / 16 | |
| 2.2.53 | 12 / 16 | |
| 2.2.52 | 12 / 16 | |
| 2.2.51 | 14 / 16 |
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.53
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 (sn-filipdanisko) than the most recent previously approved version (susergii) on 2025-12-04, but sn-filipdanisko 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.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.