← Home

@dotcom-tool-kit/containerised-app-with-assets

npm Repository Homepage

A bootstrap plugin that provides the required Tool Kit plugins for a containerised application that's deployed to Amazon Elastic Container Service (ECS,) additionally supporting building and uploading assets to S3.

11
Versions
ISC
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

quartertothe-ftrobertboulton

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@dotcom-tool-kit/webpack AI (phantom-deps): Same-org sibling plugin declared as dep for config composition; not directly imported by design. ai
phantom-deps phantom-dep:@dotcom-tool-kit/containerised-app AI (phantom-deps): Same-org sibling plugin declared as dep for config composition; not directly imported by design. ai
phantom-deps phantom-dep:@dotcom-tool-kit/upload-assets-to-s3 AI (phantom-deps): Same-org sibling plugin declared as dep for config composition; not directly imported by design. ai
phantom-deps phantom-dep:zod AI (phantom-deps): zod referenced in config/schema context; stable false positive for this config-only plugin package. ai

Versions (showing 11 of 11)

Version Deps Published
2.0.10 4 / 0
2.0.9 4 / 0
2.0.8 4 / 0
2.0.7 4 / 0
2.0.6 4 / 0
2.0.5 4 / 0
2.0.4 4 / 0
2.0.3 4 / 0
2.0.2 4 / 0
2.0.1 4 / 0
2.0.0 4 / 0

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.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.

v2.0.8

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.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.

v2.0.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.

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.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.

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.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.