← Home

@drifted/assets

npm Homepage

collection of javascript and css assets that I use on most projects and a way to package them together.

64
Versions
GPL-3.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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ussballantyne

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Consistent across all 64 versions; maintainer hasn't enabled Sigstore provenance — stable false-positive for this package. ai
publish-pattern rapid-publish AI (publish-pattern): High-frequency versioning pattern consistent across 64 releases; no malicious indicators. ai
source-diff encoded-string-file:public/dependencies.js AI (source-diff): Encoded string is base64 WASM binary (AGFzbQ magic bytes); legitimate SIMD WASM bundle, stable for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Require target is a fixed __dirname-relative path, not user-controlled; stable false positive for this package. ai
source-diff obfuscated-file:public/marked.js AI (source-diff): File is the canonical marked.js bundle (MIT, markedjs/marked); minification is expected for a bundled asset package. ai
phantom-deps phantom-dep:carrier-pigeon AI (phantom-deps): Declared dep referenced in config; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:qrcode AI (phantom-deps): Declared dep referenced in config; phantom-dep heuristic false positive for this package. ai
semgrep semgrep:new-function-constructor AI (semgrep): Fires inside vendored underscore.js template engine — standard pattern, not attacker-controlled input. ai

Versions (showing 64 of 64)

Version Deps Published
0.0.132 4 / 3
0.0.131 4 / 3
0.0.130 4 / 3
0.0.123 4 / 3
0.0.122 3 / 3
0.0.121 3 / 3
0.0.120 3 / 3
0.0.118 3 / 3
0.0.116 3 / 3
0.0.115 3 / 3
0.0.112 3 / 3
0.0.111 3 / 3
0.0.110 3 / 3
0.0.108 2 / 3
0.0.106 2 / 3
0.0.104 2 / 3
0.0.101 2 / 3
0.0.90 2 / 3
0.0.89 2 / 3
0.0.86 2 / 3
0.0.83 2 / 3
0.0.82 2 / 3
0.0.81 2 / 3
0.0.80 2 / 3
0.0.68 2 / 3
0.0.66 2 / 3
0.0.65 2 / 3
0.0.62 2 / 3
0.0.61 2 / 3
0.0.60 2 / 3
0.0.55 2 / 3
0.0.40 2 / 3
0.0.34 2 / 3
0.0.33 2 / 3
0.0.32 2 / 3
0.0.31 2 / 3
0.0.30 2 / 3
0.0.28 2 / 3
0.0.26 2 / 3
0.0.25 2 / 3
0.0.24 2 / 3
0.0.23 2 / 3
0.0.22 2 / 3
0.0.21 2 / 3
0.0.20 2 / 3
0.0.19 2 / 3
0.0.18 2 / 3
0.0.17 2 / 3
0.0.16 2 / 3
0.0.15 2 / 3
0.0.14 2 / 3
0.0.13 2 / 3
0.0.12 2 / 3
0.0.11 2 / 3
0.0.10 2 / 3
0.0.9 2 / 3
0.0.8 2 / 3
0.0.7 2 / 3
0.0.6 2 / 3
0.0.5 2 / 3
0.0.4 2 / 3
0.0.3 2 / 3
0.0.2 2 / 3
0.0.1 2 / 3

v0.0.26

1 finding
INFO No provenance attestation provenance

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

v0.0.25

1 finding
INFO No provenance attestation provenance

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

v0.0.24

1 finding
INFO No provenance attestation provenance

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

v0.0.23

1 finding
INFO No provenance attestation provenance

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

v0.0.22

1 finding
INFO No provenance attestation provenance

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

v0.0.21

1 finding
INFO No provenance attestation provenance

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

v0.0.20

1 finding
INFO No provenance attestation provenance

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

v0.0.19

1 finding
INFO No provenance attestation provenance

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

v0.0.18

1 finding
INFO No provenance attestation provenance

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

v0.0.17

1 finding
INFO No provenance attestation provenance

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

v0.0.16

1 finding
INFO No provenance attestation provenance

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

v0.0.15

1 finding
INFO No provenance attestation provenance

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

v0.0.14

1 finding
INFO No provenance attestation provenance

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

v0.0.13

1 finding
INFO No provenance attestation provenance

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

v0.0.12

1 finding
INFO No provenance attestation provenance

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

v0.0.11

1 finding
INFO No provenance attestation provenance

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

v0.0.10

1 finding
INFO No provenance attestation provenance

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

v0.0.9

1 finding
INFO No provenance attestation provenance

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

v0.0.8

1 finding
INFO No provenance attestation provenance

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

v0.0.7

1 finding
INFO No provenance attestation provenance

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

v0.0.6

1 finding
INFO No provenance attestation provenance

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

v0.0.5

1 finding
INFO No provenance attestation provenance

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

v0.0.4

1 finding
INFO No provenance attestation provenance

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

v0.0.3

1 finding
INFO No provenance attestation provenance

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

v0.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.