← Home

ultron

npm Repository Homepage

Ultron is high-intelligence robot. It gathers intel so it can start improving upon his rudimentary design

5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

unshiftv13rdeden

Keywords

Ultronrobotgatherintelligenceeventeventseventemitteremittercleanup

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change to 'unshift' reflects the legitimate transition to Arnout Kazemier's org account in 2014; stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer 'unshift' is the legitimate author org (Arnout Kazemier); transition occurred in 2014 and is well-established. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected and not a risk signal for this package. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.1 0 / 5
1.1.0 0 / 5
1.0.2 0 / 5
1.0.1 0 / 5
1.0.0 0 / 5

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

2 findings
HIGH Publisher changed: V1 → 3rdeden (on 2015-06-10) provenance

This version was published by a different npm account than previous versions on 2015-06-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

2 findings
HIGH Publisher changed: V1 → unshift (on 2014-11-11) provenance

This version was published by a different npm account than previous versions on 2014-11-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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