@supernovaio/supernova-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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer matched as known prior maintainer per provenance info. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal team turnover on long-running org package, no behavior change. | ai | |
| phantom-deps | phantom-dep:async-mutex | AI (phantom-deps): Used in config, longstanding dependency. | ai | |
| phantom-deps | phantom-dep:parse-color | AI (phantom-deps): Used in config, longstanding dependency. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.10.2 | 16 / 19 | |
| 1.10.1 | 16 / 19 | |
| 1.10.0 | 15 / 19 | |
| 1.9.57 | 15 / 19 | |
| 1.9.56 | 15 / 19 | |
| 1.9.55 | 15 / 19 | |
| 1.9.54 | 15 / 19 | |
| 1.9.53 | 15 / 19 | |
| 1.9.52 | 15 / 19 | |
| 1.9.50 | 15 / 19 | |
| 1.9.48 | 15 / 19 | |
| 1.9.47 | 15 / 19 | |
| 1.9.46 | 15 / 19 | |
| 1.9.45 | 15 / 19 | |
| 1.9.44 | 15 / 19 | |
| 1.9.43 | 15 / 19 | |
| 1.9.42 | 15 / 21 | |
| 1.9.41 | 15 / 21 | |
| 1.9.40 | 15 / 21 | |
| 1.9.39 | 15 / 21 | |
| 1.9.38 | 15 / 21 | |
| 1.9.36 | 15 / 21 | |
| 1.9.35 | 15 / 21 | |
| 1.9.34 | 15 / 21 | |
| 1.9.33 | 15 / 21 | |
| 1.9.32 | 15 / 21 | |
| 1.9.31 | 15 / 21 | |
| 1.9.30 | 15 / 21 | |
| 1.9.29 | 15 / 21 | |
| 1.9.28 | 15 / 21 | |
| 1.9.27 | 15 / 21 | |
| 1.9.26 | 15 / 21 | |
| 1.9.25 | 15 / 21 | |
| 1.9.24 | 15 / 21 | |
| 1.9.23 | 15 / 21 | |
| 1.9.22 | 15 / 21 | |
| 1.9.21 | 15 / 21 | |
| 1.9.20 | 15 / 21 | |
| 1.9.19 | 15 / 21 | |
| 1.9.18 | 15 / 21 | |
| 1.9.17 | 15 / 21 | |
| 1.9.16 | 15 / 21 | |
| 1.9.15 | 15 / 21 |
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.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 (clxsupernova) than the most recent previously approved version (susergii) on 2026-05-18, but clxsupernova 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.
v1.9.56
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 (susergii) than the most recent previously approved version (artufimtcev) on 2026-03-20, but susergii 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.
v1.9.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 (artufimtcev) than the most recent previously approved version (susergii) on 2025-06-18, but artufimtcev 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.
v1.9.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.42
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 (artufimtcev) on 2025-03-11, 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.
v1.9.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
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 (artufimtcev) than the most recent previously approved version (jiritrecak) on 2024-07-30, but artufimtcev 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.
v1.9.17
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 (artufimtcev) than the most recent previously approved version (jiritrecak) on 2024-07-18, but artufimtcev 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.
v1.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.