← Home

@pipedream/asana

npm Homepage

Pipedream Asana Components

15
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

sacerdoticasrettjkdylburgeradolfo-pddanpipedreamjasonatpipedreamalan-pipedream

Keywords

pipedreamasana

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Publisher has 38 approved packages, no rejections; dormancy gap is not unusual for org-maintained integration packages. ai
typosquat typosquat.levenshtein:async AI (typosquat): Scoped @pipedream/asana is an Asana integration component, not a typosquat of the 'async' utility library. ai
dependencies unvetted-dep:@pipedream/platform AI (dependencies): Internal Pipedream sibling dependency; stable false positive for all @pipedream/* packages. ai

Versions (showing 15 of 15)

Version Deps Published
1.1.0 2 / 0
1.0.0 2 / 0
0.12.0 2 / 0
0.11.0 2 / 0
0.10.0 2 / 0
0.9.0 2 / 0
0.8.2 2 / 0
0.8.1 2 / 0
0.8.0 2 / 0
0.7.4 2 / 0
0.7.3 2 / 0
0.7.2 2 / 0
0.7.1 2 / 0
0.7.0 2 / 0
0.6.4 2 / 0

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

1 finding
LOW No provenance attestation provenance

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

v0.8.2

1 finding
LOW No provenance attestation provenance

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

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

v0.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.1

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.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.