@norskvideo/norsk-studio-aws
ALPHA ===
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aws-sdk/client-medialive | AI (dependencies): Official AWS SDK package; stable legitimate dependency for this AWS integration package. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-translate | AI (dependencies): Official AWS SDK package; stable legitimate dependency. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-mediaconnect | AI (dependencies): Official AWS SDK package; stable legitimate dependency. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-mediapackage | AI (dependencies): Official AWS SDK package; stable legitimate dependency. | ai | |
| dependencies | unvetted-dep:@norskvideo/norsk-sdk | AI (dependencies): First-party Norsk SDK dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:@norskvideo/norsk-studio | AI (dependencies): First-party Norsk Studio dependency; expected for this package family. | ai | |
| dependencies | unvetted-dep:json-refs | AI (dependencies): Well-known OpenAPI/JSON schema utility; no malware history. | ai | |
| phantom-deps | phantom-dep:json-refs | AI (phantom-deps): May be used indirectly via config/schema processing; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:openapi-types | AI (phantom-deps): Type-only usage common for TypeScript packages; stable false positive. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.27.0 | 8 / 20 | |
| 1.11.0 | 9 / 20 | |
| 1.10.0 | 9 / 20 | |
| 1.9.0 | 9 / 20 | |
| 1.8.0 | 9 / 20 | |
| 1.7.0 | 9 / 20 | |
| 1.6.0 | 9 / 20 | |
| 1.4.0 | 7 / 20 | |
| 1.3.6 | 7 / 20 | |
| 1.3.3 | 7 / 20 | |
| 1.3.2 | 7 / 20 | |
| 1.3.1 | 7 / 20 | |
| 1.3.0 | 7 / 20 | |
| 1.1.0 | 6 / 20 |
v1.27.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.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (robashton) than the most recent previously approved version (adrianroe) on 2024-08-22, but robashton is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (robashton) than the most recent previously approved version (adrianroe) on 2024-08-01, but robashton is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adrianroe) than the most recent previously approved version (robashton) on 2024-07-23, but adrianroe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.