@altimateai/altimate-code MIT 11 versions

@altimateai/altimate-code

npm

11

Versions

MIT

License

Yes

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mdesmet_altimatesarav.altimateanandgupta1

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dbt-tools/dist/index.js	AI (source-diff): File is a standard ESM bundle (esbuild output); network+exec pattern is boilerplate module interop, not a dropper.	ai	2026/05/22
source-diff	source-size-tripled	AI (source-diff): Size increase explained by bundling dbt-tools and vendoring sqlglot Python library into dist.	ai	2026/05/22
semgrep	semgrep:child-process-import	AI (semgrep): child_process used only to run `ldd --version` for musl/Alpine detection in postinstall; benign pattern.	ai	2026/05/22
phantom-deps	phantom-dep:@altimateai/altimate-core	AI (phantom-deps): Same-org runtime dep used by the binary/postinstall layer, not directly imported in the wrapper JS — expected for this distribution pattern.	ai	2026/04/26
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall selects the correct platform-specific binary from optional deps — standard pattern for native CLI distribution (esbuild, bun, etc.). Stable for this package.	ai	2026/04/26
bogus-package	bogus-package	AI (bogus-package): Sparse metadata is typical for org-internal CLI tooling distributed under a scoped namespace with 43 versions and active downloads. Not indicative of spam or malware.	ai	2026/04/26

Versions (showing 11 of 11)

Version	Deps	Published
0.7.2	1 / 0	2026-05-21
0.5.5	1 / 0	2026-03-21
0.5.1	1 / 0	2026-03-19
0.5.0	1 / 0	2026-03-19
0.4.9	1 / 0	2026-03-18
0.4.6	0 / 0	2026-03-18
0.2.5	0 / 0	2026-03-14
0.2.4	0 / 0	2026-03-05
0.2.0	0 / 0	2026-03-04
0.1.10	0 / 0	2026-03-03
0.1.1	0 / 0	2026-03-02

v0.7.2

2 findings

HIGH New file with network + code execution: dbt-tools/dist/index.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.5

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.9

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.6

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.5

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.4

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.10

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.