← Home

@atom8n/backend-common

npm
20
Versions
—
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

atom8n-user

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@atom8n/di AI (phantom-deps): Same-org scoped; likely re-exported or used transitively in monorepo. ai
phantom-deps phantom-dep:@atom8n/config AI (phantom-deps): Same-org scoped; likely re-exported or used transitively in monorepo. ai
phantom-deps phantom-dep:@atom8n/constants AI (phantom-deps): Same-org scoped; likely re-exported or used transitively in monorepo. ai
phantom-deps phantom-dep:@atom8n/decorators AI (phantom-deps): Same-org scoped; likely re-exported or used transitively in monorepo. ai
phantom-deps phantom-dep:@atom8n/n8n-workflow AI (phantom-deps): Same-org scoped; likely re-exported or used transitively in monorepo. ai
phantom-deps phantom-dep:reflect-metadata AI (phantom-deps): Known implicit dependency for TypeScript decorators; stable pattern. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo package; missing metadata and inflated semver are normal for workspace packages. ai

Versions (showing 20 of 20)

Version Deps Published
1.5.5 10 / 3
1.5.2 10 / 3
1.5.1 10 / 3
1.5.0 10 / 3
1.4.4 10 / 3
1.4.3 10 / 3
1.4.2 10 / 3
1.4.1 10 / 3
1.4.0 10 / 3
1.3.0 10 / 3
1.2.9 10 / 3
1.2.8 10 / 3
1.2.7 10 / 3
1.2.6 10 / 3
1.2.5 10 / 3
1.2.4 10 / 3
1.2.3 10 / 3
1.2.2 10 / 3
1.2.1 10 / 3
1.2.0 10 / 3

v1.5.5

1 finding
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.

v1.5.2

1 finding
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.

v1.5.1

1 finding
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.

v1.5.0

1 finding
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.

v1.4.4

1 finding
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.

v1.4.3

1 finding
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.

v1.4.2

1 finding
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.

v1.4.1

1 finding
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.

v1.4.0

1 finding
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.

v1.3.0

1 finding
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.

v1.2.9

1 finding
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.

v1.2.8

1 finding
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.

v1.2.7

1 finding
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.

v1.2.6

1 finding
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.

v1.2.5

1 finding
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.

v1.2.4

1 finding
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.

v1.2.3

1 finding
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.

v1.2.2

1 finding
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.

v1.2.1

1 finding
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.

v1.2.0

1 finding
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.