@nativescript/audio-context Apache-2.0 15 versions

@nativescript/audio-context

npm Repository Homepage

Web Audio API for NativeScript

15

Versions

Apache-2.0

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

rigor789nativescript-bot

Keywords

NativeScriptJavaScriptTypeScriptiOSAndroidWeb Audio APIAudioContext

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): NativeScript iOS plugin; xcframework binaries are required for native iOS integration, stable pattern for this package.	ai	2026/05/27

Versions (showing 15 of 15)

Version	Deps	Published
1.2.2	0 / 0	2026-05-06
1.2.1	0 / 0	2026-05-05
1.2.0	0 / 0	2026-05-04
1.1.8	0 / 0	2026-05-04
1.1.7	0 / 0	2026-05-03
1.1.6	0 / 0	2026-05-01
1.1.5	0 / 0	2026-04-30
1.1.4	0 / 0	2026-04-30
1.1.3	0 / 0	2026-04-30
1.1.2	0 / 0	2026-04-29
1.1.1	0 / 0	2026-04-29
1.1.0	0 / 0	2026-04-29
1.0.2	0 / 0	2026-04-27
1.0.1	0 / 0	2026-04-27
1.0.0	0 / 0	2026-04-27

v1.2.2

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • platforms/ios/AudioContextNative.xcframework/ios-arm64/AudioContextNative.framework/AudioContextNative

LOW No provenance attestation provenance

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

v1.2.1

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • platforms/ios/AudioContextNative.xcframework/ios-arm64/AudioContextNative.framework/AudioContextNative

LOW No provenance attestation provenance

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

v1.2.0

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • platforms/ios/AudioContextNative.xcframework/ios-arm64/AudioContextNative.framework/AudioContextNative

LOW No provenance attestation provenance

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

v1.1.8

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • platforms/ios/AudioContextNative.xcframework/ios-arm64/AudioContextNative.framework/AudioContextNative

LOW No provenance attestation provenance

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

v1.1.7

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • platforms/ios/AudioContextNative.xcframework/ios-arm64/AudioContextNative.framework/AudioContextNative

LOW No provenance attestation provenance

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

v1.1.6

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • platforms/ios/AudioContextNative.xcframework/ios-arm64/AudioContextNative.framework/AudioContextNative

LOW No provenance attestation provenance

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

v1.1.5

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.