← Home

@plugjs/expect5

npm Repository Homepage

Unit Testing for the PlugJS Build System ========================================

100
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pfumagalli

Keywords

assertassertionbuildcompileecmascriptexpectexpectationjavascriptnodeplugjstddtesttestingtranspiletypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; stable pattern for this package going forward. ai
bogus-package bogus-package AI (bogus-package): Established package (1124 days, 189 versions) in a monorepo; sparse README is expected for a workspace sub-package. ai

Versions (showing 100 of 123)

Version Deps Published
0.6.116 1 / 2
0.6.115 1 / 2
0.6.114 1 / 2
0.6.113 1 / 2
0.6.112 1 / 2
0.6.111 1 / 2
0.6.110 1 / 2
0.6.109 1 / 2
0.6.108 1 / 2
0.6.107 1 / 2
0.6.106 1 / 2
0.6.105 1 / 2
0.6.104 1 / 2
0.6.103 1 / 2
0.6.102 1 / 2
0.6.101 1 / 2
0.6.100 1 / 2
0.6.99 1 / 2
0.6.98 1 / 2
0.6.97 1 / 2
0.6.96 1 / 2
0.6.95 1 / 2
0.6.94 1 / 2
0.6.93 1 / 2
0.6.92 1 / 2
0.6.91 1 / 2
0.6.90 1 / 2
0.6.89 1 / 2
0.6.88 1 / 2
0.6.87 1 / 2
0.6.86 1 / 2
0.6.85 1 / 2
0.6.84 1 / 2
0.6.83 1 / 2
0.6.82 1 / 2
0.6.81 1 / 2
0.6.80 1 / 2
0.6.79 1 / 2
0.6.78 1 / 2
0.6.77 1 / 2
0.6.76 1 / 2
0.6.75 1 / 2
0.6.74 1 / 2
0.6.73 1 / 2
0.6.72 1 / 2
0.6.71 1 / 2
0.6.70 1 / 2
0.6.69 1 / 2
0.6.68 1 / 2
0.6.67 1 / 2
0.6.66 1 / 2
0.6.65 1 / 2
0.6.64 1 / 2
0.6.63 1 / 2
0.6.62 1 / 2
0.6.61 1 / 2
0.6.60 1 / 2
0.6.59 1 / 2
0.6.58 1 / 2
0.6.57 1 / 2
0.6.56 1 / 2
0.6.55 1 / 2
0.6.54 1 / 2
0.6.53 1 / 2
0.6.52 1 / 2
0.6.51 1 / 2
0.6.50 1 / 2
0.6.49 1 / 2
0.6.48 1 / 2
0.6.47 1 / 2
0.6.46 1 / 2
0.6.45 1 / 2
0.6.44 1 / 2
0.6.43 1 / 2
0.6.41 1 / 2
0.6.40 1 / 2
0.6.39 1 / 2
0.6.38 1 / 2
0.6.37 1 / 2
0.6.36 1 / 2
0.6.35 1 / 2
0.6.34 1 / 2
0.6.33 1 / 2
0.6.32 1 / 2
0.6.31 1 / 2
0.6.30 1 / 2
0.6.29 1 / 2
0.6.28 1 / 2
0.6.27 1 / 2
0.6.26 1 / 2
0.6.25 1 / 2
0.6.24 1 / 2
0.6.23 1 / 2
0.6.22 1 / 2
0.6.21 1 / 2
0.6.20 1 / 2
0.6.19 1 / 2
0.6.18 1 / 2
0.6.17 1 / 2
0.6.16 1 / 2
Showing 100 of 123 Next page →

v0.6.116

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.

v0.6.115

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.

v0.6.114

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.

v0.6.113

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.

v0.6.45

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.

v0.6.44

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.

v0.6.43

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.

v0.6.41

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.

v0.6.40

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.

v0.6.39

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.

v0.6.38

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.

v0.6.37

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.

v0.6.36

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.

v0.6.35

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.

v0.6.34

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.

v0.6.33

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.

v0.6.32

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.

v0.6.31

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.

v0.6.30

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.

v0.6.29

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.

v0.6.28

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.

v0.6.27

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.

v0.6.26

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.

v0.6.25

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.

v0.6.24

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.

v0.6.23

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.

v0.6.22

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.

v0.6.21

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.

v0.6.20

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.

v0.6.19

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.

v0.6.18

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.

v0.6.17

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.

v0.6.16

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.