← Home

@jaypie/aws

npm Repository Homepage
28
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

finlaysonstudio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @jaypie/aws; Levenshtein match to 'qs' is a false positive with no brand similarity. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package @jaypie/aws; Levenshtein match to 'ajv' is a false positive with no brand similarity. ai
bogus-package bogus-package AI (bogus-package): Established monorepo package with 54 versions and SLSA provenance; sparse README is a style choice, not spam. ai

Versions (showing 28 of 28)

Version Deps Published
1.2.11 9 / 5
1.2.10 8 / 5
1.2.9 8 / 4
1.2.8 8 / 4
1.2.7 8 / 4
1.2.6 8 / 4
1.2.5 8 / 4
1.2.4 7 / 4
1.2.3 7 / 4
1.2.2 6 / 4
1.2.1 6 / 4
1.2.0 6 / 4
1.1.22 7 / 1
1.1.21 5 / 1
1.1.20 5 / 1
1.1.19 4 / 1
1.1.18 4 / 1
1.1.17 4 / 1
1.1.16 4 / 1
1.1.15 4 / 1
1.1.14 4 / 0
1.1.4 3 / 0
1.1.3 3 / 0
1.1.1 3 / 0
1.1.0 3 / 0
1.0.8 3 / 12
1.0.7 3 / 15
1.0.6 3 / 15

v1.2.11

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.20

1 finding
LOW No provenance attestation provenance

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

v1.1.19

1 finding
LOW No provenance attestation provenance

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

v1.1.18

1 finding
LOW No provenance attestation provenance

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

v1.1.17

1 finding
LOW No provenance attestation provenance

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

v1.1.16

1 finding
LOW No provenance attestation provenance

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

v1.1.15

1 finding
LOW No provenance attestation provenance

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

v1.1.14

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

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

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.