← Home

danger

npm Repository Homepage
8
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

macklinuortadangersystems

Keywords

dangerci

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Intentional plugin-loader pattern for external CI source modules; stable across versions. ai
semgrep semgrep:child-process-import AI (semgrep): danger runs subprocesses as core functionality (danger-process); expected and documented. ai
semgrep semgrep:base64-decode AI (semgrep): Decoding GitHub API file content (base64-encoded by GitHub API); standard usage. ai
dependencies unvetted-dep:pinpoint AI (dependencies): Long-standing dependency in danger's ecosystem; no malicious signals. ai
dependencies unvetted-dep:override-require AI (dependencies): Long-standing dependency in danger's ecosystem; no malicious signals. ai
dependencies unvetted-dep:memfs-or-file-map-to-github-branch AI (dependencies): danger-org owned package; stable dependency across many versions. ai

Versions (showing 8 of 8)

Version Deps Published
13.0.8 33 / 48
13.0.7 33 / 48
13.0.5 34 / 49
13.0.4 37 / 50
13.0.3 37 / 50
13.0.2 37 / 50
13.0.1 37 / 50
13.0.0 37 / 50

v13.0.4

1 finding
LOW No provenance attestation provenance

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

v13.0.3

1 finding
LOW No provenance attestation provenance

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

v13.0.2

1 finding
LOW No provenance attestation provenance

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

v13.0.1

1 finding
LOW No provenance attestation provenance

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

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