@pipedream/asana
Pipedream Asana Components
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 2 / 0 | |
| 0.11.0 | 2 / 0 | |
| 0.10.0 | 2 / 0 | |
| 0.9.0 | 2 / 0 | |
| 0.8.1 | 2 / 0 | |
| 0.8.0 | 2 / 0 |
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.