← Home

@atomicservice/ascf-base

npm

ascf base

4
Versions
MIT
License
No
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

atomicservice

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ws AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:ejs AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:tar AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:jimp AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:json5 AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:semver AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:adm-zip AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:express AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:cachedir AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai
phantom-deps phantom-dep:body-parser AI (phantom-deps): Legitimate runtime dependency; heuristic false positive for config-driven usage. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.17 11 / 8
1.0.14 6 / 8
1.0.13 6 / 8
1.0.12 6 / 8

v1.0.17

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.0.14

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.0.13

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.0.12

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.