@devrev/ts-adaas
Typescript library containing the ADaaS(AirDrop as a Service) control protocol.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package now publishes via GitHub Actions with SLSA provenance; CI/CD publisher is expected going forward. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared runtime dependency in package.json; phantom-dep is a false positive here. | ai | |
| dependencies | unvetted-dep:js-jsonl | AI (dependencies): Small JSONL parsing utility; no malware indicators; acceptable for this package's context. | ai | |
| dependencies | unvetted-dep:@devrev/typescript-sdk | AI (dependencies): First-party DevRev SDK dependency; same org as the publisher; stable pattern across versions. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.19.8 | 7 / 15 | |
| 1.19.7 | 7 / 15 | |
| 1.19.6 | 6 / 15 | |
| 1.19.5 | 7 / 15 | |
| 1.19.4 | 7 / 15 | |
| 1.19.3 | 7 / 15 | |
| 1.19.2 | 7 / 15 | |
| 1.19.1 | 7 / 15 | |
| 1.19.0 | 7 / 15 | |
| 1.18.0 | 7 / 15 | |
| 1.17.0 | 7 / 17 | |
| 1.16.0 | 8 / 18 | |
| 1.15.2 | 8 / 17 | |
| 1.15.1 | 8 / 17 | |
| 1.15.0 | 8 / 17 | |
| 1.14.1 | 8 / 17 | |
| 1.14.0 | 8 / 17 | |
| 1.13.3 | 8 / 17 | |
| 1.13.2 | 8 / 17 | |
| 1.13.1 | 8 / 17 | |
| 1.13.0 | 7 / 23 | |
| 1.12.2 | 7 / 23 | |
| 1.12.1 | 7 / 23 | |
| 1.12.0 | 7 / 23 | |
| 1.11.0 | 7 / 15 | |
| 1.10.0 | 9 / 14 | |
| 1.9.0 | 8 / 12 | |
| 1.8.1 | 8 / 12 | |
| 1.8.0 | 8 / 11 | |
| 1.7.1 | 8 / 11 | |
| 1.7.0 | 8 / 11 | |
| 1.6.0 | 8 / 12 | |
| 1.5.1 | 8 / 12 | |
| 1.5.0 | 8 / 12 | |
| 1.4.2 | 8 / 12 | |
| 1.4.1 | 8 / 12 | |
| 1.4.0 | 8 / 12 |
v1.19.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.